Mastering AWS Health Checks: Route 53, ELB, and Auto Scaling

This guide covers the critical mechanisms AWS uses to detect and remediate infrastructure and application failures, specifically focusing on Route 53, Elastic Load Balancing (ELB), and Auto Scaling Groups (ASG) as required for the DevOps Engineer Professional exam.

Learning Objectives

After studying this guide, you should be able to:

• Distinguish between System Status Checks and Instance Status Checks.
• Configure Route 53 Health Checks for endpoints, calculated checks, and CloudWatch alarms.
• Implement ELB Health Checks and understand their impact on traffic routing.
• Synchronize Auto Scaling Group health checks with ELB and manage the Health Check Grace Period.
• Design failover architectures using health check signals to meet RTO/RPO requirements.

Key Terms & Glossary

• ARP (Address Resolution Protocol): Used by EC2 instance status checks to verify network connectivity at the ENI level.
• Failure Threshold: The number of consecutive failed checks required to mark a resource as "Unhealthy."
• Health Check Grace Period: The time ASG waits after an instance enters InService before checking its health.
• InService: The state where an instance is fully launched, lifecycle hooks are complete, and it is ready for health monitoring.
• Liveness Probe: A general term for health checks that ensure an application is actually responding to requests, not just the server being "on."

The "Big Idea"

Health checks are the sensory system of a highly available architecture. Without them, the control plane (Route 53 or ALB) is blind, continuing to send traffic to