Q: How does AWS WAF protect your ALB and what rules would you set up for a web app?
WAF inspects HTTP requests before they reach the ALB. Rules: AWS Managed Rule Groups (OWASP top 10, bot control), IP rate limiting (prevent DDoS), geo-blocking, SQL injection detection, XSS detection. Set rules to block or count.
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."
Production Solution & Architecture
WAF inspects HTTP requests before they reach the ALB. Rules: AWS Managed Rule Groups (OWASP top 10, bot control), IP rate limiting (prevent DDoS), geo-blocking, SQL injection detection, XSS detection. Set rules to block or count.
- Immediate Triage: WAF inspects HTTP requests before they reach the ALB. Rules: AWS Managed Rule Groups (OWASP top
- 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 protect rules 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 protect rules 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 protect rules 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 protect rules Target instances must explicitly permit inbound HTTP/HTTPS traffic from the ALB security group on the configured container/application port.