Proper paths to use for AWS Elastic Load Balancer health checks
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
To further refine your ELB after setting it up according to How to configure Amazon Web Service Application Load Balancer with Confluence
For each ELB, you will have defined Target groups (see the KB above). Each of these Target Groups has a Health Checks tab which you can edit, for example:
Solution
The following targets should be used for the health status checks by the ELB:
Node | status check path |
|---|---|
Confluence | /status |
Synchrony | /synchrony/heartbeat |
As you can see on the screenshots above, there are definable parameters (defaults pictured). By default the ELB sends a GET request for the path defined every 30 seconds (configurable) and looks for a 200 OK response (success code).
If the status check comes back OK, your environment will work as desired. If the status check fails due to the application being down, unreachable (network issue or just too busy to respond), or the path is incorrectly defined, the ELB will serve up 5xx error to the user.
Was this helpful?