IGNITE: Terraform Practice to Enable Infrastructure Scaling
summary
Argues for organizing Terraform repositories by team/project/cloud/account/env/region with custom modules stored separately, and shows that this produces small state files, reduces spurious destroy plans, and limits blast radius to a single region/account. Describes using Terraform modules, remote state per leaf, repo-level tests/guardrails and code owners to enforce tagging, cost and policy checks while giving teams autonomy to approve their own PRs. Claims the structure improves plan accuracy and scales both infrastructure and teams.
AI-written summary · about
related talks
31mTerraform Practices to Enable Infrastructure Scaling
30mTerraform Practices to Enable Infrastructure Scaling
15mTerraform Practices: The Good, the Bad, and the Ugly
41mTerraform Practices - The Good, the Bad, and the Ugly
22mLessons Learned from Scaling Infrastructure as Code
59mManaging Terraform modules at scale
29mTerraform Practices - The Good, the Bad, and the Ugly
31mTerraform Structure & Enablement