Terraform Practices to Enable Infrastructure Scaling
summary
Recommends locking module, provider and Terraform versions to avoid unexpected breaking changes and using community modules with download-count checks (Anton Babenko examples) instead of reinventing wheels. Insists on tagging everything and using S3 backend with DynamoDB state locking for remote state. Advises one-repo layout (live + modules) split by team/project/provider/region to keep small state files, warns about workspaces and suggests a wrapper. Pushes remote execution and PR automation with Atlantis, plus pre-merge checks: fmt, TFLint, CI, Super Linter and drift reporting.
AI-written summary · about
chapters (8)
- 0:00Introduction and speaker intro
- 3:08Quick wins for Terraform scaling
- 8:50Second nature practices in Terraform
- 13:24File structure and code organization
- 15:54Long haul infrastructure planning
- 23:36Terraform execution best practices
- 25:42Practices enforcement for scaling
- 28:10Key takeaways and conclusion
related talks
39mTerraform Practices to Enable Infrastructure Scaling
30mTerraform Practices to Enable Infrastructure Scaling
41mTerraform Practices - The Good, the Bad, and the Ugly
29mTerraform Practices - The Good, the Bad, and the Ugly
35mTerraform Practices - The Good, the Bad and the Ugly
06mIGNITE: Terraform Practice to Enable Infrastructure Scaling
46mTerraform best practices with examples and arguments
15mTerraform Practices: The Good, the Bad, and the Ugly
