⚡ ~/naveed Interview Prep
⚡ Portfolio Home 👤 About Naveed Bio & Credentials 📫 Contact Naveed Get In Touch ✍️ Engineering Blog Deep Dives 🎯 Interview Hub 1,000+ Scenarios ☸️ Kubernetes Mastery Hub 24 Modules 🎮 DevOps Arcade & Quizzes Subnet Blitz ⚡ 🗺️ DevOps Roadmaps PDFs & Guides 🤖 Morpheus Analysis AI Quant ↗ 🛠️ Developer Tools Utilities 🧪 Labs & Experiments 📄 Interactive CV & Certs 🔗 All Links & Socials ⚡ Join The Dispatch (Weekly SRE Newsletter) →
← Back to All Terraform & IaC Interview Questions Scenario 16 of 120 in Terraform & IaC
Senior DevOps / SRE [L2] Terraform Import & Migrations Production Scenario [L2]
🎯 Target Role / Context: Terraform Scenario #11 (L2) · Import & Migrations

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:

#Terraform #Import & Migrations #L2 #IaC #Cloud Infrastructure #Terraform State
🎙️ Candidate Opening & Architectural Context
""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.""
Advertisement
⚡ Recommended Practice Lab

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."

1️⃣

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.
2️⃣

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 plan shows no changes.
💡 The Senior SRE Gold Nugget (Key Architectural Takeaway)
"Pro-Tip: Write the Terraform resource configuration first (what the resource should look like in code).."
⚡ 60-Second Elevator Pitch Talking Points
  • 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.
⛔ Critical Candidate Mistakes to Avoid in This Scenario

Senior hiring managers and bar raisers evaluate how you prioritize during outages. Avoid these common anti-patterns:

  1. 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.
  2. 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.
  3. 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.
  4. 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.
Advertisement
Want more Terraform & IaC scenarios?
Explore our complete collection of scenario-based Terraform & IaC interview runbooks.
Browse All Terraform & IaC Questions →