Announcing preview for Amazon Route 53 Application Recovery Controller zonal shift
Amazon Route 53 Application Recovery Controller now supports zonal shift to help you quickly recover from application failures in an AWS Availability Zone (AZ). Starting today, you can shift application traffic away from using an AZ with a single action for multi-AZ resources with support of Application Load Balancer and Network Load Balancer. This will help you quickly recover an unhealthy application in an AZ, and reduce the duration and severity of impact to the application due to events such as power outages and hardware or software failures.
Amazon Route 53 Application Recovery Controller now supports zonal shift to help you quickly recover from application failures in an AWS Availability Zone (AZ). Starting today, you can shift application traffic away from using an AZ with a single action for multi-AZ resources with support of Application Load Balancer and Network Load Balancer. This will help you quickly recover an unhealthy application in an AZ, and reduce the duration and severity of impact to the application due to events such as power outages and hardware or software failures.
To initiate a zonal shift you can simply go to the Amazon Route 53 Application Recovery Controller console to start a zonal shift for a load balancer in your AWS account, in an AWS Region. You can also use the AWS SDK to start a zonal shift and programmatically move application traffic out of an AZ, and move it back once the affected AZ is healthy. Zonal shift is available for Application Load Balancers and Network Load Balancers with cross-zone configuration disabled.
There is no additional charge for using zonal shift. Zonal shift is now available in: US East (Ohio), US East (Northern Virginia), US West (Oregon), Europe (Ireland), Asia Pacific (Tokyo), Asia Pacific (Sydney), Europe (Frankfurt), Europe (Stockholm), and Asia Pacific (Jakarta). To get started, read the launch blog, visit the Amazon Route 53 Application Recovery Controller page, or read the documentation.