Route 53 Health Checks works once and then switches to Failed immediately

Hi,

The topic "How Amazon Route 53 determines whether a health check is healthy" in the Route 53 Developer Guide says:

"Route 53 considers a new health check to be healthy until there's enough data to determine the actual status, healthy or unhealthy."

https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/dns-failover-determining-health-of-endpoints.html

If you post your domain name, I'll take a look at your DNS configuration.

Scott

The Health Check is supposed to check if a service that runs under port 3272 responds to HTTP requests.

The port 3272 is open to the public and I can curl it from my external computer, but the route 53 health check fails:

curl -I 3.80.197.207:3272/connect
HTTP/1.1 200 OK
Content-Length: 300
Content-Type: Json
Server: CockpitMain Microsoft-HTTPAPI/2.0
Date: Wed, 15 Apr 2020 15:41:16 GMT

Edited by: hyperdanny on Apr 15, 2020 8:35 AM

I have done more testing and I think my application can not keep up with the timeout time of 2 secs.
My application needs at least 5 seconds.

Is there a way to get this changed?

Hi,

Can you change to TCP health checks? For HTTP and HTTPS health checks, Route 53 must establish a connection within four seconds. For TCP health checks, it's 10 seconds. For details, see "How Route 53 determines the status of health checks that monitor an endpoint":

https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/dns-failover-determining-health-of-endpoints.html#dns-failover-determining-health-of-endpoints-monitor-endpoint

Scott