Q: Your ALB target group is showing all instances as unhealthy. What do you check?
1. Health check path — does the path exist? curl http://<instance-ip>:<health-check-port><health-check-path> from the ALB's subnet.
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."
Initial Diagnostics & Root Cause Analysis
- Health check path — does the path exist?
curl http://from the ALB's subnet.: - Security group — the ALB's Security Group must be allowed to reach the instance on the health check port. Add inbound rule to instance SG: allow from ALB SG.
- Instance running the app — is the application actually running on that port?
netstat -tlnp | grep.
Remediation & Permanent Safeguards
- Health check port — is it the traffic port or a different one? Misconfiguration here is common.
- Response code — the health check expects 200. If the app returns 301 redirect, that's a failure by default. Add 301 to success codes or fix the redirect.
- Health check path — does the path exist? curl http://: from the ALB's subnet.
- Security group — the ALB's Security Group must be allowed to reach the instance on the health che...
- Instance running the app — is the application actually running on that port? netstat -tlnp | grep .
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 target group showing 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 target group showing 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 target group showing 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 target group showing Target instances must explicitly permit inbound HTTP/HTTPS traffic from the ALB security group on the configured container/application port.