Q: Terraform state has grown very large and every plan is slow. What changes would you consider?
Split infrastructure by lifecycle and ownership so one state file does not contain unrelated resources. Avoid storing large rendered temp...
#Terraform #Use VPC ID from another module #L2 #IaC #Cloud Infrastructure #Terraform State
🎙️ Candidate Opening & Architectural Context
""Managing infrastructure as code across multiple teams requires disciplined state management and locking. 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
🛠️ Production Runbook & Step-by-Step Resolution
1️⃣
Production Solution & Architecture
Split infrastructure by lifecycle and ownership so one state file does not contain unrelated resources. Avoid storing large rendered templates, generated files, or unnecessary outputs in state. Remove resources from state only when they should no longer be managed, and prefer smaller root modules that can be planned independently. Large state increases lock time, review noise, and blast radius.
💡 The Senior SRE Gold Nugget (Key Architectural Takeaway)
"Pro-Tip: Split infrastructure by lifecycle and ownership so one state file does not contain unrelated resources. Avoid storing large render."
⚡ 60-Second Elevator Pitch Talking Points
- Immediate Triage: Split infrastructure by lifecycle and ownership so one state file does not contain unrelated re
- Run targeted verification commands before modifying configuration.
- Automate permanent guardrails (CI check, alerts, IaC policy) to prevent recurrence.
Advertisement