There are a number of HTTP endpoints that the Aurora scheduler exposes. These allow various operational tasks to be performed on the scheduler. Below is an (incomplete) list of such endpoints and a brief explanation of what they do.
The /leaderhealth endpoint enables performing health checks on the scheduler instances inorder to forward requests to the leading scheduler. This is typically used by a load balancer such as HAProxy or AWS ELB.
When a HTTP GET request is issued on this endpoint, it responds as follows:
200 OKis returned.
503 SERVICE_UNAVAILABLEis returned.
502 BAD_GATEWAYis returned.