REL13-BP05 Automate recovery
Use AWS or third-party tools to automate system recovery and route traffic to the DR site or Region.
Based on configured health checks, AWS services, such as Elastic Load Balancing and AWS Auto Scaling, can distribute load to healthy Availability Zones while services, such as Amazon Route 53 and AWS Global Accelerator, can route load to healthy AWS Regions. Amazon Route 53 Application Recovery Controller helps you manage and coordinate failover using readiness check and routing control features. These features continually monitor your application’s ability to recover from failures, so you can control application recovery across multiple AWS Regions, Availability Zones, and on premises.
For workloads on existing physical or virtual data centers or private clouds, AWS Elastic Disaster Recovery
Common anti-patterns:
-
Implementing identical automated failover and failback can cause flapping when a failure occurs.
Benefits of establishing this best practice: Automated recovery reduces your recovery time by eliminating the opportunity for manual errors.
Level of risk exposed if this best practice is not established: Medium
Implementation guidance
Automate recovery paths. For short recovery times, follow your disaster recovery plan
to get your IT systems back online quickly in the case of a disruption. -
Use Elastic Disaster Recovery for automated Failover and Failback. Elastic Disaster Recovery continuously replicates your machines (including operating system, system state configuration, databases, applications, and files) into a low-cost staging area in your target AWS account and preferred Region. In the case of a disaster, after choosing to recover using Elastic Disaster Recovery, Elastic Disaster Recovery automates the conversion of your replicated servers into fully provisioned workloads in your recovery Region on AWS.
-
Resources
Related documents:
Related videos:
