Q: What is an Elastic Load Balancer and what are the differences between ALB, NLB, and CLB?
- CLB (Classic Load Balancer) — legacy. Avoid for new projects. Layer 4 and Layer 7 but limited features.
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: "In a previous role, our monitoring paged me for a similar incident across our AWS VPC infrastructure. 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
Choose: ALB for web apps/APIs. NLB for TCP/UDP or when you need static IP. GWLB for network security appliances.
- CLB (Classic Load Balancer) — legacy. Avoid for new projects. Layer 4 and Layer 7 but limited features.
- ALB (Application Load Balancer) — Layer 7 (HTTP/HTTPS). Content-based routing: route by URL path, hostname, headers, query strings. Best for microservices and HTTP apps. Supports WebSockets, HTTP/2.
- NLB (Network Load Balancer) — Layer 4 (TCP/UDP/TLS). Ultra-low latency. Handles millions of requests per second. Static IP / Elastic IP support. Best for high-performance, non-HTTP workloads (game servers, IoT, VoIP).
Remediation & Permanent Safeguards
- GWLB (Gateway Load Balancer) — for inline network appliances (firewalls, IDS/IPS). Newer addition.
- CLB (Classic Load Balancer) — legacy. Avoid for new projects. Layer 4 and Layer 7 but limited fea...
- ALB (Application Load Balancer) — Layer 7 (HTTP/HTTPS). Content-based routing: route by URL path,...
- NLB (Network Load Balancer) — Layer 4 (TCP/UDP/TLS). Ultra-low latency. Handles millions of reque...
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 Elastic Load Balancer 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 Elastic Load Balancer 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 Elastic Load Balancer 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 Elastic Load Balancer Target instances must explicitly permit inbound HTTP/HTTPS traffic from the ALB security group on the configured container/application port.