- Newest
- Most votes
- Most comments
Hi,
When there is an AZ failure, the health checks on the ALB would fail on the basis of unhealthy threshold and stop sending traffic to the instance in failed AZ. The health checks continue in the background and when the AZ recovers the instance is marked healthy after meeting the success threshold. For the duration that the EC2 remains unhealthy due to the supposed AZ failure, the ASG health checks define what happens to the unhealthy instance (if the instances were part of the ASG & ideally should be for multi AZ config). The default is EC2 health checks in ASG, which means that the instance would be replaced only if the instance has a hardware failure and is impaired. You can also set it to ELB health check type in ASG, where the instance would be auto replaced due to being marked unhealthy by the ALB and to maintain the desired count
If you manually added the instances in different AZ to the ALB ( ie. no ASG), then the instance would only be marked unhealthy and not receive traffic for the duration of the AZ failure but wont be terminated. Once the AZ recovers, the instance would start receiving traffic.
Some useful links:
https://docs.aws.amazon.com/autoscaling/ec2/userguide/ec2-auto-scaling-health-checks.html https://docs.aws.amazon.com/autoscaling/ec2/userguide/as-add-elb-healthcheck.html
--Syd
Relevant content
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a month ago