Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

What specificaly is involved in an Elastic Load Balancer health check on an instance?

I know that it performas an HTTP(S) "ping"; does it just deem an instance "Unhealthy" if that HTTP request returns an error status $THRESHOLD number of times in a row?

Or does it take other factors into account, such as CPU usage?

share|improve this question
up vote 9 down vote accepted

There are only 2 factors taken into account:

For TCP: Failure to connect within the configured timeout is considered unhealthy.

For HTTP: Any answer other than "200 OK" within the timeout period is considered unhealthy.

... and of course you need to specify the Timeout and UnhealthyThreshold which will determine how many failures before the instance is flagged Unhealthy.

share|improve this answer

No just the protocol of either HTTP or TCP at this time. With HTTP you can define a "Ping Path" which can point to a file on the web server to make sure not only is the web server up and running but a expected page in rendering, but that's basically it. Thresholds, timeouts, and intervals are all customizable but again only for the HTTP and TCP protocols.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.