Health Checks in Route 53 monitor the availability of resources (e.g., EC2, load balancers) by sending HTTP, HTTPS, or TCP requests. They ensure traffic is routed only to healthy resources and can trigger failover when a resource becomes unhealthy.
Key Features:
- Monitor Resources: HTTP, HTTPS, or TCP checks.
- Health Evaluation: Based on status codes (e.g., 2xx/3xx for healthy).
- Customizable: Set intervals, failure thresholds, and path for HTTP/HTTPS checks.
- Failover Routing: Redirect traffic to healthy endpoints if a resource fails.
- CloudWatch Integration: Alarms for failed checks.
- Global Monitoring: Performed from multiple locations worldwide.
Health Check Types:
- HTTP/HTTPS: Checks a specific URL path (e.g.,
/healthcheck).
- TCP: Verifies if a connection can be made on a specific port.
Example:
- Resource: EC2 instance with a
/healthcheck endpoint.
- Type: HTTP
- Path:
/healthcheck
- Failure Threshold: 3 failed attempts
- Interval: Every 30 seconds