Terraform Practices to Enable Infrastructure Scaling
summary
Opinionated checklist: lock Terraform, provider and module versions to avoid surprise breaking changes; use S3 backend + DynamoDB lock for remote state and enable S3 versioning; enforce tagging with provider default tags and PR checks; split code by team/project/provider/region to keep state files small and reduce spurious destroys; prefer verified community modules or maintain stateless reusable modules; run CI checks (terraform fmt, tflint) and Atlantis PR automation or GitHub Actions to generate plans and require plan files before apply — this is what Wix uses successfully.
AI-written summary · about
chapters (13)
- 0:00Introduction and speaker intro
- 2:05Quick wins for Terraform scaling
- 5:43Daily best practices for Terraform
- 8:11Variables and locals in Terraform
- 11:42File structure and code organization
- 13:07Applying classic code practices
- 14:53Long-term Terraform collaboration
- 17:22Codebase structure for scaling
- 21:56State files and workspaces
- 22:17Remote execution and safety
- 24:02Practices enforcement in Terraform
- 27:10Company needs and infrastructure vision
- 28:11Summary and key takeaways
related talks
39mTerraform Practices to Enable Infrastructure Scaling
31mTerraform Practices to Enable Infrastructure Scaling
29mTerraform Practices - The Good, the Bad, and the Ugly
35mTerraform Practices - The Good, the Bad and the Ugly
41mTerraform Practices - The Good, the Bad, and the Ugly
06mIGNITE: Terraform Practice to Enable Infrastructure Scaling
15mTerraform Practices: The Good, the Bad, and the Ugly
46mTerraform best practices with examples and arguments