Q: Your S3 backend bucket for Terraform state was deleted by mistake but the infrastructure still exists. What is your recovery path?
First recreate the backend bucket and locking table if needed. Restore the latest valid state from S3 versioning or backup; if no backup ...
#Terraform #Use VPC ID from another module #L2 #IaC #Cloud Infrastructure #S3
🎙️ 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
First recreate the backend bucket and locking table if needed. Restore the latest valid state from S3 versioning or backup; if no backup exists, create a fresh backend and rebuild state by importing resources with terraform import. After recovery, enable versioning, restrict delete permissions, and document the backend as critical infrastructure so it is protected like production data.
💡 The Senior SRE Gold Nugget (Key Architectural Takeaway)
"Pro-Tip: First recreate the backend bucket and locking table if needed. Restore the latest valid state from S3 versioning or backup; if no ."
⚡ 60-Second Elevator Pitch Talking Points
- Immediate Triage: First recreate the backend bucket and locking table if needed. Restore the latest valid state f
- Run targeted verification commands before modifying configuration.
- Automate permanent guardrails (CI check, alerts, IaC policy) to prevent recurrence.
Advertisement