service health check
A regular automatic test, run by a load balancer, Auto Scaling group or container service, of whether a copy of a service can really handle requests.
In more detail
A load balancer sends a request to each target and stops routing to targets that fail; an Auto Scaling group or ECS service replaces copies that stay unhealthy. A good check tests the path users need, not just whether a process exists, because a running process can still be unable to serve. Repeated failures need logs and metrics to explain them, or automatic replacement just repeats a broken release.
Example
An Auto Scaling group with healthCheck set to load-balancer replaces instances the load balancer marks unhealthy.Related terms
- target group — The set of servers, containers or functions a load balancer forwards requests to, with the health check that judges them.
- Auto Scaling group — An EC2 feature that keeps a desired number of identical instances running, replacing failed ones and adding or removing them as load changes.
- load balancer — A server that spreads incoming requests across several copies of a service so no single copy is overloaded.
Taught in
- Load Balancing and DNS — Cloud Infrastructure & Hyperscaler Architecture
- Elastic Compute Cloud (EC2) — Cloud Infrastructure & Hyperscaler Architecture
- Containers on AWS (ECS and EKS) — Cloud Infrastructure & Hyperscaler Architecture
- Serverless Compute (Lambda) — Cloud Infrastructure & Hyperscaler Architecture
- Comparing Compute Options — Cloud Infrastructure & Hyperscaler Architecture
- Auto Scaling Groups — Cloud Infrastructure & Hyperscaler Architecture