AWS Elastic Disaster Recovery (AWS DRS) is the recommended service for disaster recovery to AWS. It provides similar capabilities as CloudEndure Disaster Recovery, and is operated from the AWS Management Console. This enables seamless integration between AWS DRS and other AWS services, such as AWS CloudTrail, AWS Identity and Access Management (IAM), and Amazon CloudWatch.
With AWS Elastic Disaster Recovery, you can recover your applications on AWS from physical infrastructure, VMware vSphere, Microsoft Hyper-V, and cloud infrastructure. You can also use AWS Elastic Disaster Recovery to recover Amazon EC2 instances in a different AWS Region.
You can use AWS Elastic Disaster Recovery to recover all of your applications and databases that run on supported Windows and Linux operating system versions.
AWS Elastic Disaster Recovery currently supports the following AWS Regions: US East (Ohio), US East (N. Virginia), US West (Oregon), Asia Pacific (Singapore), Asia Pacific (Sydney), Asia Pacific (Tokyo), Europe (Frankfurt), Europe (Ireland), and Europe (London). Please refer to the AWS Regional Services List for the most up-to-date information on Region support.
We recommend using CloudEndure Disaster Recovery only if you require one or more of the following capabilities:
- Replication to an AWS Region not yet supported by AWS Elastic Disaster Recovery
- Replication of an operating system not yet supported by AWS Elastic Disaster Recovery
- Replication of more than 300 servers that need to recover to the same AWS Region and AWS account
- HIPAA or ISO compliance
- Replication and recovery into AWS Outposts
Detailed comparison of CloudEndure Disaster Recovery and AWS Elastic Disaster Recovery
Capability | CloudEndure Disaster Recovery | AWS Elastic Disaster Recovery (AWS DRS) |
Operating system (OS) support |
|
|
Recovery Region support |
|
|
Console and APIs |
|
|
AWS resource management |
|
|
User management and monitoring |
|
|
Consumption model | Hourly metering via AWS Marketplace subscription that requires an additional EULA |
Hourly metering via standard AWS billing and EULA |
Pricing |
|
|
Control plane |
|
|
Public internet access |
|
|
Temporary IAM credentials for agent installation | No |
Yes |
Non-disruptive failback testing |
|
|
AWS Region to Region replication and recovery | Yes |
Yes |
AWS Region to Region failback | Yes |
Yes, but currently requires manual steps |
Large-scale failback automation | Yes |
Yes |
Separate accounts for staging and launching (Required for deployments with more than 300 servers per AWS account per target Region) |
Yes |
No |
No rescan on reboot | Supported for Windows only |
Supported for Windows and Linux |
In scope for the following compliance programs |
|
|
Pause/resume replication | Yes |
No |
Stop replication | Yes |
Requires uninstalling the AWS DRS agent |
Start replication | Yes |
Requires reinstalling the AWS DRS agent |
AWS Region to Region VPC stack creation | Yes |
No |
Auto-detection of added disks | Yes |
No |
Support for AWS Outposts | Yes |
No |
Recovery plans | Yes |
See this blog post for instructions |
Additional resources

Start replicating your servers to AWS.

Get prescriptive guidance for disaster recovery of on-premises applications to AWS.

Follow steps to set up, test, and operate AWS DRS.