AWS Elastic Disaster Recovery Features

The launch management settings in AWS DRS let you control how recovery instances will be launched for your source servers. You can define default launch settings to apply to newly added source servers, as well as modify launch settings in bulk for existing source servers, providing a simple method for you to manage source servers at scale. For applications running on AWS, you can also modify the recovery Availability Zone (AZ) for multiple source servers, which helps simplify cross-AZ recovery.

Using post-launch actions on AWS DRS, you can define actions that run automatically after launching recovery instances. You can create custom actions for any AWS Systems Manager (AWS SSM) command or automation, including documents you create or that were shared with you. You can also use a pre-defined set of actions, such as installing a CloudWatch agent, volume free space detection, instances network connectivity verification, volume integrity validation, or creating an Amazon Machine Image from the instance.

AWS DRS makes it easy to replicate and recover your AWS network components and configurations to maintain the readiness and security of your AWS recovery site. These components include subnet settings (such as CIDR), security groups, route tables, Internet gateways, and network ACLs. Automating the replication of your network (VPC) configuration substantially increases the chances of a smooth and rapid recovery. It also enhances security and saves time and resources.

AWS DRS allows you to recover into an original or pre-defined existing instance instead of spinning up a new Amazon EC2 instance. By being able to recover into an existing instance, you can retain the existing metadata and security parameters associated with the instance.