Recovery readiness with an existing application
With Amazon Route 53 Application Recovery Controller, you can understand the recovery readiness of your application and prepare for failover. If you have an existing application, take the following steps before you set up Route 53 ARC for it:
Identify the application that you want to set up with recovery readiness.
Review the definitions of the components in Route 53 ARC. For more information, see Readiness check components .
Review the information in Recovery readiness with a new application.
Set up the required user (or users), roles, and policies for Route 53 ARC. For more information, see Security in Amazon Route 53 Application Recovery Controller.
To set up the structure in Route 53 ARC that enables recovery readiness, you can use the Route 53 ARC API – for example, by using the Amazon CLI – or the Amazon Web Services Management Console. You can also use Amazon CloudFormation or HashiCorp Terraform templates to quickly get started with Route 53 ARC.
Using one of these options, you model replicas, or failure-containment units, for your
application. Within each replica, you define the resources that your application uses,
such as Amazon EC2 Auto Scaling groups and load balancers. You can then understand the recovery
readiness of your application as a whole, or as individual replicas within your
application. You can view readiness status by using API actions, such as
get-recovery-readiness
, or by reviewing readiness status in the
console. For more information, see Monitoring readiness status in Route 53 ARC.
If you already have an application that you want to set up readiness checks for, Route 53 ARC can analyze your application configuration and provide specific guidance for how to make it more recovery-oriented. For more information, see Getting architecture recommendations in Route 53 ARC.
Route 53 ARC also continually scans your application architectures and Amazon Route 53 routing policies to detect issues. For more information, see DNS target resource readiness checks: Auditing resiliency readiness.