Resources supported for zonal shifts - Amazon Route 53 Application Recovery Controller

Resources supported for zonal shifts

Amazon Route 53 Application Recovery Controller currently supports zonal shifts for Network Load Balancers and Application Load Balancers. Both public and internal (private) Network Load Balancers and Application Load Balancers are supported. You can start a zonal shift for a load balancer in the Elastic Load Balancing console or in Route 53 ARC.

Review the following conditions for working with zonal shifts and resources in Route 53 ARC:

  • Zonal shift isn't supported with cross-zone load balancing. For a load balancer to be registered with Route 53 ARC, make sure that you've turned off cross-zone load balancing for the load balancer in ELB.

  • A resource must be active and fully provisioned to shift traffic for it. Before you start a zonal shift for a resource, check to make sure that it's a managed resource in Route 53 ARC. For example, you can view the list of managed resources in the AWS Management Console, or you can use the get-managed-resource operation with the resource's identifier.

  • Zonal shift isn't supported for Application Load Balancers that are endpoints of accelerators in AWS Global Accelerator.

  • When an Application Load Balancer is the target of a Network Load Balancer, start the zonal shift from the Network Load Balancer. If you start the zonal shift from the Application Load Balancer, the Network Load Balancer doesn't stop sending traffic to the Application Load Balancer and its targets.

  • The resource for a zonal shift must be a managed resource that has been registered with Route 53 ARC by an AWS service. Elastic Load Balancing automatically registers with Route 53 ARC Network Load Balancers and Application Load Balancers with cross-zone load balancing turned off.

  • To start a zonal shift with a resource, it must be deployed in the Availability Zone and AWS Region where you start the shift. Make sure that you start a zonal shift in the same Region that the AZ for the shift is in, and that the resource you're shifting traffic for is in the same AZ and Region as well.

  • Make sure that you have the correct IAM permissions to use zonal shift with a resource. For more information, see IAM and permissions for zonal shift.