Q: Infrastructure was created manually in the AWS console. Your team now wants to manage it with Terraform. How do you import it?
Use terraform import:
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."
Initial Diagnostics & Root Cause Analysis
Use terraform import:
- Write the Terraform resource configuration first (what the resource should look like in code).
- Import the resource into state:
- Run
terraform plan— it will show diffs between your config and the actual resource.
Remediation & Permanent Safeguards
For large-scale imports: Terraformer or tf-import can auto-generate Terraform code from existing AWS resources. New in Terraform 1.5: import blocks in configuration files — declarative import as code.
terraform import aws_instance.my_server i-1234567890abcdef0
- Fix the config to match reality until
planshows no changes.
- Write the Terraform resource configuration first (what the resource should look like in code).
- Import the resource into state:
- Run terraform plan — it will show diffs between your config and the actual resource.
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 created manually console 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 created manually console 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 created manually console 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 created manually console Unpinned provider versions automatically download breaking major upgrades during CI runs, introducing unexpected schema validation failures.