Q: You need to provision identical infrastructure across 10 AWS regions. How do you structure this in Terraform without duplicating code 10 times?
Use the for_each meta-argument with a module:
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 the for_each meta-argument with a module: Define a provider per region using aliases: Or use Terragrunt with a generate block that creates provider config per region dynamically. Separate state files per region (separate backend key per region) for independent management.
variable "regions" {
default = ["us-east-1", "us-west-2", "eu-west-1", ...]
}
module "regional_infra" {
for_each = toset(var.regions)
source = "./modules/regional"
providers = {
aws = aws.by_region[each.key]
}
region = each.key
}
- Immediate Triage: Use the for_each meta-argument with a module:
- 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 need provision identical 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 need provision identical 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 need provision identical 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 need provision identical Unpinned provider versions automatically download breaking major upgrades during CI runs, introducing unexpected schema validation failures.