Common Pitfalls When Using Terraform and How to Avoid Them
summary
Covers concrete missteps: hard‑coding AWS or Google service keys causes leaked creds and CI failures, so prefer temporary credentials or CI OIDC (GitHub/GitLab) and leave provider blocks empty; shows SSL certificate rotation on Google Cloud where the API has no update method and prescribes creating the new cert, attach to LB, detach old cert, then delete it using name_prefix with lifecycle to force safe ordering; gives exact bug report checklist: Terraform and provider versions, debug logs, minimal repro.
AI-written summary · about
chapters (5)
- 0:00Introduction
- 0:52Secure authentication
- 3:47Handling tricky resources
- 7:03Getting help and docs
- 9:56Reporting bugs
related talks
32mGotchas Using Terraform in a Secure Delivery Pipeline
01h 00mGotchas using Terraform in a secure delivery pipeline
31mHow Secure are Your Sensitive Values in Terraform? Common Pitfalls of Scale Factory's Clients
14mLightning Talk: 5 Security Tips for Terraform
31mTerraform Modules & Providers: Check Your Source
05mUsing Terraform Safely
08mLighting Talk: Lessons Learned from Writing Thousands of Lines of IaC
17mAdvance securely: Safely migrating to