Q: How do you manage Terraform infrastructure across 50 AWS accounts in an AWS Organization?
Use a CI/CD system per account (GitHub Actions with OIDC, separate role per account). Shared modules in a central registry. Terragrunt or Terraform Cloud for orchestration.
Want to master this scenario in a live sandbox? KodeKloud's HashiCorp Certified Terraform Associate (003) Interactive Labs covers this exact problem with hands-on terminal drills.
🛠️ Production Runbook & Step-by-Step Resolution
Direct Answer: "In our enterprise Terraform repository, we designed reusable modules and remote backends to prevent this exact issue. When addressing this question, I walk the interviewer through our production incident runbook: isolating the blast radius, checking diagnostic logs and metrics, and applying a safe fix."
Production Solution & Architecture
Use a CI/CD system per account (GitHub Actions with OIDC, separate role per account). Shared modules in a central registry. Terragrunt or Terraform Cloud for orchestration. Account vending machine (Control Tower) creates new accounts pre-wired for Terraform.
- Immediate Triage: Use a CI/CD system per account (GitHub Actions with OIDC, separate role per account). Shared mo
- Run targeted verification commands before modifying configuration.
- Automate permanent guardrails (CI check, alerts, IaC policy) to prevent recurrence.
Senior hiring managers and bar raisers evaluate how you prioritize during outages. Avoid these common anti-patterns:
- Executing Terraform applies without inspecting '# forces replacement' warnings in plan output when configuring manage Terraform across Attributes that force resource replacement destroy and recreate critical infrastructure (databases, load balancers), inducing unannounced production outages.
- Omitting remote state locking mechanisms (DynamoDB or backend native locks) for shared state files when configuring manage Terraform across Without state locking, concurrent CI/CD pipeline executions or team applies create race conditions that corrupt the state file.
- Structuring entire enterprise cloud footprints into a single monolithic Terraform root module when configuring manage Terraform across Monolithic state files slow plan execution dramatically, increase blast radius during failed applies, and create severe pipeline locking contention.
- Failing to pin required_providers versions, causing breaking provider upgrades in CI pipelines when configuring manage Terraform across Unpinned provider versions automatically download breaking major upgrades during CI runs, introducing unexpected schema validation failures.