Terraform Practices to Enable Infrastructure Scaling
summary
Shows concrete practices: lock module and provider versions and enforce tagging; store state in an S3 backend + DynamoDB state lock with versioning; split state by team/project/provider/region to keep state files small and avoid Terraform invalid-dependency destroys; prefer vetted community modules, put logic in modules not live code, use TF files for per-region variables and locals for constants, set timeouts and remote execution, and run automated checks (tflint, tf fmt) and Atlantis to apply and auto-merge so main equals running infra.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 2:10Quick wins for scaling
- 7:28Daily practices
- 14:54File structure
- 17:04Code best practices
- 19:14Planning infrastructure
- 21:43Terraform as a platform
- 24:35Using Terraform workspaces effectively
- 27:23State and execution
- 29:53Enforcement and guardrails
- 33:06Key takeaways
- 35:16Q&A
related talks
30mTerraform Practices to Enable Infrastructure Scaling
31mTerraform Practices to Enable Infrastructure Scaling
29mTerraform Practices - The Good, the Bad, and the Ugly
46mTerraform best practices with examples and arguments
48mCodifying Infrastructure with Terraform for the Future
35mMisadventures with Terraform
29mInfinity and beyond: Scaling Terraform for the global enterprise
47mHow to build scale & maintain 45 pub Terraform mod. with over 100 million provisions