Advanced Iac Iot
Skill Profile
(Select at least one profile to enable specific modules)
Overview
Advanced Infrastructure as Code (IaC) for IoT enables automated, reproducible, and scalable infrastructure management across distributed IoT environments. This skill encompasses Terraform for infrastructure provisioning, Ansible for configuration management, and GitOps for continuous deployment, ensuring consistent infrastructure across thousands of edge devices and cloud resources.
Why This Matters
- Scalability: Manage thousands of IoT devices programmatically
- Consistency: Ensure identical infrastructure across environments
- Reproducibility: Recreate infrastructure from version-controlled code
- Speed: Deploy infrastructure in minutes instead of days
- Reliability: Reduce human error through automation
Core Concepts & Rules
1. Core Principles
- Follow established patterns and conventions
- Maintain consistency across codebase
- Document decisions and trade-offs
2. Implementation Guidelines
- Start with the simplest viable solution
- Iterate based on feedback and requirements
- Test thoroughly before deployment
Inputs / Outputs / Contracts
- Inputs:
- Infrastructure specifications (VPC, subnets, gateways)
- Configuration parameters (firmware, locations, deployment ID)
- Git repository URLs and credentials
- Entry Conditions:
- Cloud account configured with appropriate permissions
- Git repository initialized
- CI/CD pipeline configured
- Outputs:
- Provisioned infrastructure resources
- Configured IoT devices
- Deployed applications
- State files and outputs
- Artifacts Required (Deliverables):
- Terraform modules and configurations
- Ansible playbooks and inventories
- ArgoCD application manifests
- Helm charts
- Acceptance Evidence:
- Terraform plan shows no changes
- Ansible playbook completes successfully
- ArgoCD applications synced
- Infrastructure resources provisioned
- Success Criteria:
- Deployment time < 10 minutes
- Configuration drift 0%
- Success rate > 99%
- Rollback time < 5 minutes
- Compliance 100%
Skill Composition
Quick Start / Implementation Example
- Review requirements and constraints
- Set up development environment
- Implement core functionality following patterns
- Write tests for critical paths
- Run tests and fix issues
- Document any deviations or decisions
# Example implementation following best practices
def example_function():
# Your implementation here
pass
Assumptions / Constraints / Non-goals
- Assumptions:
- Development environment is properly configured
- Required dependencies are available
- Team has basic understanding of domain
- Constraints:
- Must follow existing codebase conventions
- Time and resource limitations
- Compatibility requirements
- Non-goals:
- This skill does not cover edge cases outside scope
- Not a replacement for formal training
Compatibility & Prerequisites
- Supported Versions:
- Python 3.8+
- Node.js 16+
- Modern browsers (Chrome, Firefox, Safari, Edge)
- Required AI Tools:
- Code editor (VS Code recommended)
- Testing framework appropriate for language
- Version control (Git)
- Dependencies:
- Language-specific package manager
- Build tools
- Testing libraries
- Environment Setup:
.env.example keys: API_KEY, DATABASE_URL (no values)
Test Scenario Matrix (QA Strategy)
| Type |
Focus Area |
Required Scenarios / Mocks |
| Unit |
Core Logic |
Must cover primary logic and at least 3 edge/error cases. Target minimum 80% coverage |
| Integration |
DB / API |
All external API calls or database connections must be mocked during unit tests |
| E2E |
User Journey |
Critical user flows to test |
| Performance |
Latency / Load |
Benchmark requirements |
| Security |
Vuln / Auth |
SAST/DAST or dependency audit |
| Frontend |
UX / A11y |
Accessibility checklist (WCAG), Performance Budget (Lighthouse score) |
Technical Guardrails & Security Threat Model
1. Security & Privacy (Threat Model)
- Top Threats: Injection attacks, authentication bypass, data exposure
2. Performance & Resources
3. Architecture & Scalability
4. Observability & Reliability
Agent Directives & Error Recovery
(ข้อกำหนดสำหรับ AI Agent ในการคิดและแก้ปัญหาเมื่อเกิดข้อผิดพลาด)
- Thinking Process: Analyze root cause before fixing. Do not brute-force.
- Fallback Strategy: Stop after 3 failed test attempts. Output root cause and ask for human intervention/clarification.
- Self-Review: Check against Guardrails & Anti-patterns before finalizing.
- Output Constraints: Output ONLY the modified code block. Do not explain unless asked.
Definition of Done (DoD) Checklist
Anti-patterns / Pitfalls
- ⛔ Don't: Log PII, catch-all exception, N+1 queries
- ⚠️ Watch out for: Common symptoms and quick fixes
- 💡 Instead: Use proper error handling, pagination, and logging
Reference Links & Examples
- Internal documentation and examples
- Official documentation and best practices
- Community resources and discussions
Versioning & Changelog
- Version: 1.0.0
- Changelog:
- 2026-02-22: Initial version with complete template structure
Converted and distributed by TomeVault — claim your Tome and manage your conversions.
1---2name: advanced-iac-iot3description: Advanced Infrastructure as Code (IaC) for IoT enables automated, reproducible, Use when this capability is needed.4---56# Advanced Iac Iot78## Skill Profile9*(Select at least one profile to enable specific modules)*10- [ ] **DevOps**11- [x] **Backend**12- [ ] **Frontend**13- [ ] **AI-RAG**14- [ ] **Security Critical**1516## Overview17Advanced Infrastructure as Code (IaC) for IoT enables automated, reproducible, and scalable infrastructure management across distributed IoT environments. This skill encompasses Terraform for infrastructure provisioning, Ansible for configuration management, and GitOps for continuous deployment, ensuring consistent infrastructure across thousands of edge devices and cloud resources.1819## Why This Matters20- **Scalability**: Manage thousands of IoT devices programmatically21- **Consistency**: Ensure identical infrastructure across environments22- **Reproducibility**: Recreate infrastructure from version-controlled code23- **Speed**: Deploy infrastructure in minutes instead of days24- **Reliability**: Reduce human error through automation2526---2728## Core Concepts & Rules2930### 1. Core Principles31- Follow established patterns and conventions32- Maintain consistency across codebase33- Document decisions and trade-offs3435### 2. Implementation Guidelines36- Start with the simplest viable solution37- Iterate based on feedback and requirements38- Test thoroughly before deployment394041## Inputs / Outputs / Contracts42* **Inputs**:43 - Infrastructure specifications (VPC, subnets, gateways)44 - Configuration parameters (firmware, locations, deployment ID)45 - Git repository URLs and credentials46* **Entry Conditions**:47 - Cloud account configured with appropriate permissions48 - Git repository initialized49 - CI/CD pipeline configured50* **Outputs**:51 - Provisioned infrastructure resources52 - Configured IoT devices53 - Deployed applications54 - State files and outputs55* **Artifacts Required (Deliverables)**:56 - Terraform modules and configurations57 - Ansible playbooks and inventories58 - ArgoCD application manifests59 - Helm charts60* **Acceptance Evidence**:61 - Terraform plan shows no changes62 - Ansible playbook completes successfully63 - ArgoCD applications synced64 - Infrastructure resources provisioned65* **Success Criteria**:66 - Deployment time < 10 minutes67 - Configuration drift 0%68 - Success rate > 99%69 - Rollback time < 5 minutes70 - Compliance 100%7172## Skill Composition73* **Depends on**: [Hardware Rooted Identity](../74-iot-zero-trust-security/hardware-rooted-identity/SKILL.md)74* **Compatible with**: [Chaos Engineering for IoT](../76-iot-infrastructure/chaos-engineering-iot/SKILL.md), [GitOps for IoT Infrastructure](../76-iot-infrastructure/gitops-iot-infrastructure/SKILL.md)75* **Conflicts with**: Manual infrastructure management76* **Related Skills**: [Chaos Engineering for IoT](../76-iot-infrastructure/chaos-engineering-iot/SKILL.md), [GitOps for IoT Infrastructure](../76-iot-infrastructure/gitops-iot-infrastructure/SKILL.md), [Multi-Cloud IoT Strategy](../76-iot-infrastructure/multi-cloud-iot/SKILL.md)7778---7980## Quick Start / Implementation Example81821. Review requirements and constraints832. Set up development environment843. Implement core functionality following patterns854. Write tests for critical paths865. Run tests and fix issues876. Document any deviations or decisions8889```python90# Example implementation following best practices91def example_function():92 # Your implementation here93 pass94```959697## Assumptions / Constraints / Non-goals9899* **Assumptions**:100 - Development environment is properly configured101 - Required dependencies are available102 - Team has basic understanding of domain103* **Constraints**:104 - Must follow existing codebase conventions105 - Time and resource limitations106 - Compatibility requirements107* **Non-goals**:108 - This skill does not cover edge cases outside scope109 - Not a replacement for formal training110111112## Compatibility & Prerequisites113114* **Supported Versions**:115 - Python 3.8+116 - Node.js 16+117 - Modern browsers (Chrome, Firefox, Safari, Edge)118* **Required AI Tools**:119 - Code editor (VS Code recommended)120 - Testing framework appropriate for language121 - Version control (Git)122* **Dependencies**:123 - Language-specific package manager124 - Build tools125 - Testing libraries126* **Environment Setup**:127 - `.env.example` keys: `API_KEY`, `DATABASE_URL` (no values)128129130## Test Scenario Matrix (QA Strategy)131132| Type | Focus Area | Required Scenarios / Mocks |133| :--- | :--- | :--- |134| **Unit** | Core Logic | Must cover primary logic and at least 3 edge/error cases. Target minimum 80% coverage |135| **Integration** | DB / API | All external API calls or database connections must be mocked during unit tests |136| **E2E** | User Journey | Critical user flows to test |137| **Performance** | Latency / Load | Benchmark requirements |138| **Security** | Vuln / Auth | SAST/DAST or dependency audit |139| **Frontend** | UX / A11y | Accessibility checklist (WCAG), Performance Budget (Lighthouse score) |140141142## Technical Guardrails & Security Threat Model143144### 1. Security & Privacy (Threat Model)145* **Top Threats**: Injection attacks, authentication bypass, data exposure146- [ ] **Data Handling**: Sanitize all user inputs to prevent Injection attacks. Never log raw PII147- [ ] **Secrets Management**: No hardcoded API keys. Use Env Vars/Secrets Manager148- [ ] **Authorization**: Validate user permissions before state changes149150### 2. Performance & Resources151- [ ] **Execution Efficiency**: Consider time complexity for algorithms152- [ ] **Memory Management**: Use streams/pagination for large data153- [ ] **Resource Cleanup**: Close DB connections/file handlers in finally blocks154155### 3. Architecture & Scalability156- [ ] **Design Pattern**: Follow SOLID principles, use Dependency Injection157- [ ] **Modularity**: Decouple logic from UI/Frameworks158159### 4. Observability & Reliability160- [ ] **Logging Standards**: Structured JSON, include trace IDs `request_id`161- [ ] **Metrics**: Track `error_rate`, `latency`, `queue_depth`162- [ ] **Error Handling**: Standardized error codes, no bare except163- [ ] **Observability Artifacts**:164 - **Log Fields**: timestamp, level, message, request_id165 - **Metrics**: request_count, error_count, response_time166 - **Dashboards/Alerts**: High Error Rate > 5%167168169## Agent Directives & Error Recovery170*(ข้อกำหนดสำหรับ AI Agent ในการคิดและแก้ปัญหาเมื่อเกิดข้อผิดพลาด)*171172- **Thinking Process**: Analyze root cause before fixing. Do not brute-force.173- **Fallback Strategy**: Stop after 3 failed test attempts. Output root cause and ask for human intervention/clarification.174- **Self-Review**: Check against Guardrails & Anti-patterns before finalizing.175- **Output Constraints**: Output ONLY the modified code block. Do not explain unless asked.176177178## Definition of Done (DoD) Checklist179180- [ ] Tests passed + coverage met181- [ ] Lint/Typecheck passed182- [ ] Logging/Metrics/Trace implemented183- [ ] Security checks passed184- [ ] Documentation/Changelog updated185- [ ] Accessibility/Performance requirements met (if frontend)186187188## Anti-patterns / Pitfalls189190* ⛔ **Don't**: Log PII, catch-all exception, N+1 queries191* ⚠️ **Watch out for**: Common symptoms and quick fixes192* 💡 **Instead**: Use proper error handling, pagination, and logging193194195## Reference Links & Examples196197* Internal documentation and examples198* Official documentation and best practices199* Community resources and discussions200201202## Versioning & Changelog203204* **Version**: 1.0.0205* **Changelog**:206 - 2026-02-22: Initial version with complete template structure207208---209> Converted and distributed by [TomeVault](https://tomevault.io/claim/amnadtaowsoam) — claim your Tome and manage your conversions.210<!-- tomevault:4.0:skill_md:2026-04-13 -->