Comparing zonal shift and routing control in Amazon Route 53 Application Recovery Controller
Zonal shift and routing control in Amazon Route 53 Application Recovery Controller can both achieve rapid recovery and help maintain resilience for Amazon applications. Both options are highly available and help support recovery in scenarios when you have increased latency or reduced availability. Both also enable you to recover applications quickly by moving traffic, limiting the impact and time lost from issues.
Routing control is primarily focused on Amazon applications that are in multiple Amazon Regions, while zonal shift only supports Amazon applications with load balancers in multi-Availability Zone (multi-AZ) deployments. There are other differences as well.
The information in this section describes some of the key features of each option and how they compare to each other. These descriptions can help you better understand how each might apply to your organization's disaster recovery needs.
| Routing control | Zonal shift |
|---|---|
|
Regional Reroutes traffic from one Amazon Region to another (primarily) Can also be used to reroute across Availability Zones |
Zonal Moves traffic away from an Availability Zone Traffic goes to other Availability Zones in the Region, not to a specific target |
|
Requires setup Requires configuration and setup |
Available without setup Enabled automatically by supported services (currently Network Load Balancer and Application Load Balancer) |
|
Fee-based Requires separate charges for routing control |
Included with services Moving traffic away from AZs is included for supported load balancers |
|
Does not expire Traffic can be rerouted to a replica indefinitely |
Temporary All zonal shifts must be set to expire |
To learn more about each of these features, see the following chapters: