aws network_error ai_generated true

Route 53 health check failed: endpoint returned non-2xx/3xx status

ID: aws/aws-route53-health-check

Also available as: JSON · Markdown
85%Fix Rate
87%Confidence
70Evidence
2023-01-01First Seen

Version Compatibility

VersionStatusIntroducedDeprecatedNotes
2 active — — —

Root Cause

Route 53 health check reports endpoint as unhealthy due to connectivity, response code, or response content issues.

generic

Workarounds

  1. 88% success Ensure the endpoint security group allows inbound from Route 53 health checker IP ranges 
    Allow inbound from Route 53 health check IPs (published in ip-ranges.json) on the health check port

    Sources: https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/route-53-ip-addresses.html

  2. 85% success Verify the health check endpoint returns 2xx/3xx and matches the string search pattern 
    Test the endpoint directly: curl -v ENDPOINT_URL and verify response code and body match health check config

    Sources: https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/health-checks-types.html

Dead Ends

Common approaches that don't work:

  1. Disable the health check to stop failover 85% fail

    Disabling health checks removes DNS failover protection, routing traffic to dead endpoints

  2. Lower the failure threshold to be less sensitive 70% fail

    Lower thresholds mask real problems; users may hit the unhealthy endpoint

Error Chain

Leads to:
Frequently confused with: