Route 53 Routing and Failover
Explore how AWS Route 53 health checks monitor endpoint health by simulating user requests across multiple regions. Learn to configure routing policies like failover, weighted, and latency routing to ensure traffic is directed to responsive resources. Understand integration with CloudWatch alarms and SNS notifications to maintain application availability and resilience.
We'll cover the following...
Route 53 health checks are periodic tests determining whether a specified endpoint, such as a web server, an Elastic Load Balancer, or a custom IP, is healthy and responsive. These checks help Route 53 decide where to direct user traffic.
As a developer, consider health checks, automated probes that constantly validate the application’s availability. When used with CloudWatch alarms, they can monitor public endpoints or even internal services.
How health checks work
Route 53 performs health checks by mimicking real user interactions, sending HTTP, HTTPS, or TCP requests to network endpoints such as web servers, load balancers, or any IP address or domain name that resolves to an IP address.
Each health check runs independently from multiple AWS locations. If the endpoint fails in most of those regions, Route 53 considers it unhealthy. We can configure thresholds for how many consecutive ...