We Ditched Terraform 1.10 for CloudFormation: Reducing IaC Complexity for Our Small AWS Team We’re a 4-person engineering team managing 32 AWS resources across dev, staging, and production environments for a B2B SaaS product. For 18 months, we relied on Terraform 1.10 to manage our infrastructure as code (IaC). But by Q3 2024, the overhead of maintaining Terraform outweighed its benefits for our use case. Here’s why we switched to AWS CloudFormation, how we migrated, and the results. Our Terraform 1.10 Pain Points Terraform is an industry-standard IaC tool, but for our small, AWS-only team, it introduced unnecessary complexity: State file management headaches: We corrupted our S3-backed state file twice in 6 months, leading to hours of manual reconciliation. Terraform 1.10’s state locking occasionally failed, causing concurrent apply errors. Versioning and compatibility issues: Upgrading from Terraform 1.9 to 1.10 broke 3 of our custom modules due to HCL syntax changes.…