Q: A child module accidentally creates resources in the default AWS account instead of the intended aliased provider. What went wrong?
The root module likely did not pass the aliased provider into the child module, or the child module did not declare the provider configuration aliases it expects.
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: "Treat Terraform code with the same rigor as application code: pre-merge plans, state locks, and automated drift detection. 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
The root module likely did not pass the aliased provider into the child module, or the child module did not declare the provider configuration aliases it expects. Pass providers explicitly in the module block and validate the account with aws_caller_identity where account mistakes are high risk. Provider aliases do not automatically flow into every module the way many teams assume.
- Immediate Triage: The root module likely did not pass the aliased provider into the child module, or the child 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 child module accidentally 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 child module accidentally 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 child module accidentally 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 child module accidentally Unpinned provider versions automatically download breaking major upgrades during CI runs, introducing unexpected schema validation failures.