Terraform Practices - The Good, the Bad, and the Ugly
summary
Covers practical, proven Terraform moves: lock provider and Terraform versions and store state in S3 with DynamoDB state locking and S3 versioning so concurrent applies and rollbacks stop breaking environments; enforce resource tagging via CI checks to enable cost reporting; prefer verified community modules or maintain internal modules with validations; keep state small by splitting repos per team/project/region to limit blast radius; run remote execution with plan files, sensible timeouts, and use Atlantis for PR-driven plan+apply so main matches deployed state.
AI-written summary · about
chapters (16)
- 0:00Terraform practices intro
- 1:29Disclaimers
- 2:13Quick wins for scaling
- 6:35Resource tagging importance
- 8:00Daily Terraform practices
- 10:49Variables vs locals
- 15:54Maintainable Terraform code
- 18:01Terraform code best practices
- 20:26Long-term scalable practices
- 23:58Team and infra scaling
- 27:50Terraform workspaces
- 31:47Code structure planning
- 33:11Remote execution best practices
- 34:57Pre-merge checks
- 38:51Aligning infra with needs
- 39:33Terraform success takeaways
related talks
35mTerraform Practices - The Good, the Bad and the Ugly
29mTerraform Practices - The Good, the Bad, and the Ugly
15mTerraform Practices: The Good, the Bad, and the Ugly
30mTerraform Practices to Enable Infrastructure Scaling
31mTerraform Practices to Enable Infrastructure Scaling
01h 00mGotchas using Terraform in a secure delivery pipeline
35mMisadventures with Terraform
46mTerraform best practices with examples and arguments