Q: `terraform plan` takes 45 minutes because it reads hundreds of data sources across accounts and regions. How would you improve it?
First identify the slow resources and data sources from provider logs or CI timing. Replace broad data-source lookups with explicit input...
#Terraform #Use VPC ID from another module #L3 #IaC #Cloud Infrastructure #VPC
🎙️ Candidate Opening & Architectural Context
""When terraform plan shows unexpected changes, my golden rule is: never apply blindly. Investigate the diff first. 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
First identify the slow resources and data sources from provider logs or CI timing. Replace broad data-source lookups with explicit inputs where possible, split unrelated infrastructure into separate state files, and avoid refreshing stacks that do not need to change. For shared IDs like VPCs or subnets, publish stable values through SSM Parameter Store or a controlled output contract instead of scanning cloud APIs every plan.
💡 The Senior SRE Gold Nugget (Key Architectural Takeaway)
"Pro-Tip: First identify the slow resources and data sources from provider logs or CI timing. Replace broad data-source lookups with explici."
⚡ 60-Second Elevator Pitch Talking Points
- Immediate Triage: First identify the slow resources and data sources from provider logs or CI timing. Replace bro
- Run targeted verification commands before modifying configuration.
- Automate permanent guardrails (CI check, alerts, IaC policy) to prevent recurrence.
Advertisement