Terraform best practices with examples and arguments
summary
Opinionated, practical guidance for Terraform at scale: uses community resource modules and company infrastructure modules (some public modules hit ~4 million downloads), prefers Terraform 0.12 for authoring complex modules (an S3 module shrinks from ~6,000 to ~100 lines), recommends Terragrunt to orchestrate many single-module state folders, warns to avoid provider blocks, never use provisioners, and calls workspaces are evil; shows real AWS patterns and when the approach actually works.
AI-written summary · about
chapters (8)
- 0:00Start
- 0:24Anton Babenko
- 13:15Resource modules
- 16:27Infrastructure modules
- 18:13Provisioner - evil
- 23:25All-in-one
- 33:59Terraform 0.12
- 35:13Summary
related talks
46mTerraform best practices with examples and arguments
48mCodifying Infrastructure with Terraform for the Future
31mTerraform Practices to Enable Infrastructure Scaling
30mTerraform Practices to Enable Infrastructure Scaling
35mTerraform Practices - The Good, the Bad and the Ugly
31mTerraform Structure & Enablement
41mTerraform Practices - The Good, the Bad, and the Ugly
34mTerraform: A Novel About Modules, Providers, Security, and Pain