Lessons Learned from Writing Thousands of Lines of IaC
summary
Shares concrete Terraform practices from thousands of lines of IaC: use reusable modules and DRY modules with versioning, query cloud state via data sources for dynamic AMIs, store remote state in S3 with S3 + DynamoDB locking and offsite backups, encrypt state and never edit it manually, scan community modules for hidden cross‑account IAM or secrets, run drift detection with driftctl/terraform plan, and use Terragrunt/Crossplane/Pulumi where they reduce drift or improve workflow.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 1:12Why use IaC
- 3:02DRY pattern in IaC
- 8:23Terraform state files
- 13:01Using data sources
- 14:51IaC in CI/CD pipelines
- 17:25State file security
- 18:48Key takeaways
- 19:32Q&A session
related talks
22mLessons Learned from Scaling Infrastructure as Code
31mTerraform Practices to Enable Infrastructure Scaling
30mTerraform Practices to Enable Infrastructure Scaling
41mTerraform Practices - The Good, the Bad, and the Ugly
35mTerraform Practices - The Good, the Bad and the Ugly
06mIGNITE: Terraform Practice to Enable Infrastructure Scaling
01h 00mGotchas using Terraform in a secure delivery pipeline
26mTerraform Infrastructure as Code: Best Practices and Common Mistakes