Codifying Infrastructure with Terraform for the Future
summary
Concrete advice for using Terraform: prefer small, versioned resource modules from the Registry (about 650 AWS modules available) and compose them into org-level infrastructure modules; avoid provider blocks inside modules and no provisioners (they break reuse and autoscaling). Use a one-per-directory invocation pattern or Terragrunt to orchestrate dependencies, protect secrets by splitting state and using Atlantis for centralized applies, and migrate to Terraform 0.12 (beta) for for_each, richer types, and simpler syntax. A Cloudcraft → Terraform exporter is provided that generates working module-structured code.
AI-written summary · about
chapters (11)
- 0:00Introduction and speaker intro
- 2:04Terraform usage and community projects
- 7:08Terraform modules overview
- 11:28Writing resource modules
- 19:25Terraform modules best practices
- 24:11Structuring Terraform code
- 28:09Working with lists and data sources
- 33:59Testing and Terraform pitfalls
- 36:54Future of Terraform and Terraform 0.12
- 40:33Cloudcraft and infrastructure visualization
- 45:50Terraform state management and Q&A
related talks
46mTerraform best practices with examples and arguments
46mTerraform best practices with examples and arguments
39mTerraform Practices to Enable Infrastructure Scaling
31mTerraform Practices to Enable Infrastructure Scaling
30mTerraform Practices to Enable Infrastructure Scaling
35mTerraform Practices - The Good, the Bad and the Ugly
10mInfrastructure as a Code Best Practices with Terraform
31mTerraform Structure & Enablement