Q: How does AWS handle availability zones and how should you design for AZ failure?
Each AZ is a physically separate data center (separate power, cooling, networking). AZs in same region connected via low-latency links. Design: deploy in min 2 AZs (preferably 3). Use Multi-AZ RDS.
Want to master this scenario in a live sandbox? Stephane Maarek's AWS Certified DevOps Engineer Professional Masterclass on Udemy covers this exact problem with hands-on terminal drills.
🛠️ Production Runbook & Step-by-Step Resolution
Direct Answer: "AWS reliability requires differentiating between AWS control plane limits and host-level resource exhaustion. 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."
Production Solution & Architecture
Each AZ is a physically separate data center (separate power, cooling, networking). AZs in same region connected via low-latency links. Design: deploy in min 2 AZs (preferably 3). Use Multi-AZ RDS. Use ALB (automatically multi-AZ). Use ECS/ASG with instances spread across AZs. Don't use AZ-specific resources for critical state.
- Immediate Triage: Each AZ is a physically separate data center (separate power, cooling, networking). AZs in same
- Run targeted verification commands before modifying configuration.
- Automate permanent guardrails (CI check, alerts, IaC policy) to prevent recurrence.
Senior hiring managers and bar raisers evaluate how you prioritize during outages. Avoid these common anti-patterns:
- Confusing ALB 502 Bad Gateway (target connection reset) with 504 Gateway Timeout (upstream response timeout) when configuring handle availability zones 502 indicates the backend target closed the TCP connection prematurely or returned malformed HTTP, whereas 504 means the target failed to respond before idle timeout.
- Setting target deregistration delay to zero instead of allowing connection draining when configuring handle availability zones Instant target deregistration severs in-flight HTTP requests during auto-scaling scale-in or rolling deployments, causing immediate user-facing drops.
-
Failing to query CloudWatch ELB metrics (
HTTPCode_ELB_5XXvsHTTPCode_Target_5XX) during load balancer outages when configuring handle availability zones Comparing load balancer generated errors against target generated errors immediately isolates whether the issue lies in the proxy tier or application runtime. - Overlooking Security Group rules on backend EC2/ECS instances that block health check traffic from the ALB when configuring handle availability zones Target instances must explicitly permit inbound HTTP/HTTPS traffic from the ALB security group on the configured container/application port.