infrastructure-as-codelisted

# Infrastructure as Code ## Overview Tool-agnostic IaC best practices covering the decision framework, testing pyramid, CI/CD integration, state management, and policy enforcement. Includes Terraform-focused examples as the most common tool. ## Tool Selection Decision Matrix | Factor | Terraform | CloudFormation | CDK | Pulumi | |--------|-----------|---------------|-----|--------| | **Multi-cloud** | Excellent | AWS only | AWS (multi via constructs) | Excellent | | **Language** | HCL | JSON/YAML | TypeScript/Python/Java | TypeScript/Python/Go | | **State** | External (S3, etc.) | AWS-managed | AWS-managed | Pulumi Cloud or self-hosted | | **Ecosystem** | Largest provider registry | AWS-native | Growing | Growing | | **Learning curve** | Moderate (HCL) | Low (declarative) | Low (familiar lang) | Low (familiar lang) | | **Testing** | Native tests + Terratest | TaskCat, cfn-lint | CDK assertions | Pulumi testing | | **Best for** | Multi-cloud, large teams | AWS-only shops | AWS devs who prefer code | Devs who dislike DSLs | **Recommendation**: Default to Terraform for multi-cloud or large teams. Use CDK/Pulumi if team strongly prefers general-purpose languages. Use CloudFormation if AWS-only and team already knows it. ## Project Structure ### Terraform Layout ``` infrastructure/ ├── modules/ # Reusable modules │ ├── vpc/ │ │ ├── main.tf │ │ ├── variables.tf │ │ ├── outputs.tf │ │ └── README.md │ ├── eks/ │ ├── rds/ │ └── lambda