3 ms·
Ask HN: How to determine the failure of availability zone?
Been seeing a lot of instances of downtime or degraded service with cloud providers these days.
The AWS Well-Architected [1] suggests to spread the service over multiple AZ's to reduce downtime.
In case of AZ failure, is there any API to determine the status of AZ dynamically or do we rely on own health checks to determine corrective action? Is AWS Health API [2] any useful? Can it be made cloud-agnostic?
[1] https://aws.amazon.com/architecture/well-architected/
[2] https://docs.aws.amazon.com/health/latest/ug/health-api.html
- btown 7y agoThere are lots of reasons that your instances in an AZ or cloud could all go down, other than the AZ's/cloud's operator self-reporting failure! For instance, what if someone wanted to do a rolling update starting in one AZ, and it starts to saturate a limited resource in that AZ halfway through, that doesn't affect the overall AZ but does affect your instances therein? Your internal health checks, rebalancing, and monitoring should be what you use to determine your health and trigger rebalancing.