End-to-end recovery from AZ impairments in Amazon EKS using EKS Zonal shift and Istio
Containers Blog
This article explains how to implement end-to-end recovery from Availability Zone impairments in Amazon EKS using zonal shift and Istio service mesh.
- Addresses gray failures: AZ degradation that appears healthy but impacts customer experience
- Combines NLB zonal shift, EKS zonal shift, and Istio to manage three traffic patterns
- NLB zonal shift removes impaired AZ from load balancer DNS routing
- EKS zonal shift removes pods from impaired AZ via EndpointSlice updates
- Istio ServiceEntry and DestinationRule enable locality-aware routing to external dependencies
- Aurora writer failover required if primary resides in impaired AZ
- Includes sample application deployment walkthrough and cleanup procedures
This comprehensive approach ensures applications maintain performance during AZ disruptions by redirecting all inbound, internal, and outbound traffic away from degraded zones.
The AWS News Feed is currently looking for gold sponsors. If you want to support the AWS community and reach a large audience of AWS professionals, consider sponsoring the AWS News Feed.
Related articles
Nov 19
2024
2024
Monitoring and automating recovery from AZ impairments in Amazon EKS with Istio and ARC Zonal Shift
Sep 18
2025
2025
Implementing granular failover in multi-Region Amazon EKS
Oct 22
2024
2024
Amazon Application Recovery Controller zonal shift and zonal autoshift extends support for two new multi-AZ resources
May 6
2024
2024
Enhancing Network Resilience with Istio on Amazon EKS
The AWS News Feed is currently looking for silver sponsors. If you want to support the AWS community and reach a large audience of AWS professionals, consider sponsoring the AWS News Feed.