Terraform best practices with examples and arguments
summary
Practical rules and reproducible examples: treat Terraform modules as the unit of reuse — resource modules (no providers, no secrets) and infrastructure modules compose them; a popular AWS security-group module is ~600 lines and has ~1.5M downloads so reuse beats hand-rolling. Avoid provisioners; use cloud-init or null_resource only when unavoidable. Use Terragrunt to orchestrate many modules, use Atlantis + private registry instead of Terraform Enterprise for small teams, and restrict workspaces only for PR branches and providers out of modules.
AI-written summary · about
chapters (12)
- 0:00Introduction and speaker background
- 3:36Infrastructure as code with Terraform
- 7:27Terraform vs other IaC tools
- 9:59Managing AWS network stack
- 11:06Terraform modules explained
- 16:10Common module mistakes
- 22:34Structuring Terraform configurations
- 27:35Terraform workspaces drawbacks
- 31:37Terraform 0.12 features
- 34:09Terraform for developers vs users
- 39:52Q&A on Terraform 0.12
- 41:44Q&A on Terraform Enterprise
related talks
46mTerraform best practices with examples and arguments
48mCodifying Infrastructure with Terraform for the Future
35mTerraform Practices - The Good, the Bad and the Ugly
31mTerraform Practices to Enable Infrastructure Scaling
30mTerraform Practices to Enable Infrastructure Scaling
39mTerraform Practices to Enable Infrastructure Scaling
31mTerraform Structure & Enablement
41mTerraform Practices - The Good, the Bad, and the Ugly