No more typing reviews! Try our Samantha, our new voice AI agent.

Pros & Cons summary

Buyer's Guide

Get pricing advice, tips, use cases and valuable features from real users of this product.
Get the report

Prominent pros & cons

PROS

AWS Elastic Disaster Recovery significantly improves uptime, reducing downtime and ensuring business continuity during high-impact natural disasters.
AWS Elastic Disaster Recovery facilitates seamless scalability and is cost-effective, providing a stable solution for disaster recovery needs.
The straightforward initial setup of AWS Elastic Disaster Recovery and its ease of use allow for quick deployment to meet business requirements.
AWS Elastic Disaster Recovery provides seamless integration with AWS services like ACL, EKS, and Fargate, supporting containerized applications with ease.
With AWS Elastic Disaster Recovery, organizations benefit from automated orchestration of recovery processes and near real-time replication, enhancing resilience and recovery capabilities.

CONS

Customer support for AWS Elastic Disaster Recovery could be improved, as response times can be slow.
An enhanced logging system is needed to provide customers with more detailed information.
Bandwidth consumption is a concern due to constant upload communication to the AWS DR environment.
The initial setup and replication process of AWS Elastic Disaster Recovery is challenging to understand.
AWS Elastic Disaster Recovery is considered expensive, and a more cost-effective pricing model is recommended.
 

AWS Elastic Disaster Recovery Pros review quotes

it_user405462 - PeerSpot reviewer
VP Engineering at a tech services company with 501-1,000 employees
Mar 14, 2016
The ability to replicate our database and our data from one cloud to another is the most valuable feature.
SharePoi2b31 - PeerSpot reviewer
SharePoint Lead
Mar 8, 2018
We have never had any issues with scalability.
GlobalIn47b7 - PeerSpot reviewer
Global Insurance Consultant at a tech services company with 10,001+ employees
Apr 11, 2018
Scalability is pretty good; it's seamless and can do it automatically.
Learn what your peers think about AWS Elastic Disaster Recovery. Get advice and tips from experienced pros sharing their opinions. Updated: April 2026.
886,576 professionals have used our research since 2012.
Director6974 - PeerSpot reviewer
Director, IT Operations & Information Systems at a media company with 501-1,000 employees
Jul 23, 2018
We went from an organization with minimal to no disaster recovery. I was able to spin up the disaster recovery environment with AWS rather quickly and meet business requirements.
Jaydeep Bose - PeerSpot reviewer
Associate Manager at Course5 Intelligence
Jan 30, 2020
The initial setup is pretty straightforward, it's not complex.
reviewer1267797 - PeerSpot reviewer
Technology Manager with 1-10 employees
Feb 9, 2020
For regular backup and restore solutions, this product is fine.
MB
Cloud Consultant at sonata information Technology Limited
Apr 28, 2022
The solution is dependent on the network bandwidth. For example, if they have a bandwidth of 10Mbps the solution will run a little heavier. If the bandwidth is good the solution runs well.
RK
Lead DBA at a computer software company with 501-1,000 employees
May 12, 2022
It's on the cheaper side and not too expensive for users.
Jonathan Pehau - PeerSpot reviewer
Infrastructure analyst specialized in cloud computing at IT2GO Solutions
Mar 9, 2023
The most valuable aspect of CloudEndure Disaster Recovery is its instant block replication feature. This allows us to perform live block verification and eliminates the need to concern ourselves with recovery point objectives. This capability is particularly advantageous for critical workloads.
EG
AWS Solution Engineer at a tech services company with 51-200 employees
Apr 11, 2023
The setup is pretty straightforward.
 

AWS Elastic Disaster Recovery Cons review quotes

it_user405462 - PeerSpot reviewer
VP Engineering at a tech services company with 501-1,000 employees
Mar 14, 2016
It could be a bit more automated.
SharePoi2b31 - PeerSpot reviewer
SharePoint Lead
Mar 8, 2018
Sometimes a server will get a bit behind. ​
GlobalIn47b7 - PeerSpot reviewer
Global Insurance Consultant at a tech services company with 10,001+ employees
Apr 11, 2018
Definitely there should be better logging. From a customer perspective I would like to see more logs on what is happening. If there is an issue, I would like to know what the problem is. Right now, we have to depend on the support of the vendor to check and let us know, because we don't have access to a lot of logging information.
Learn what your peers think about AWS Elastic Disaster Recovery. Get advice and tips from experienced pros sharing their opinions. Updated: April 2026.
886,576 professionals have used our research since 2012.
Director6974 - PeerSpot reviewer
Director, IT Operations & Information Systems at a media company with 501-1,000 employees
Jul 23, 2018
The bandwidth is a constant upload communication to the AWS DR environment, so if you do not have the proper bandwidth, it will definitely eat up your internet line.
Jaydeep Bose - PeerSpot reviewer
Associate Manager at Course5 Intelligence
Jan 30, 2020
The user interface, customer support, and the recovery time for the current customer query could use improvement.
reviewer1267797 - PeerSpot reviewer
Technology Manager with 1-10 employees
Feb 9, 2020
I would like to see better support for creating and working with archives.
MB
Cloud Consultant at sonata information Technology Limited
Apr 28, 2022
CloudEndure Disaster Recovery is charging clients $20 to do the DR backups. It is an expensive solution.
RK
Lead DBA at a computer software company with 501-1,000 employees
May 12, 2022
I have not seen any areas that need improvement at this time.
Jonathan Pehau - PeerSpot reviewer
Infrastructure analyst specialized in cloud computing at IT2GO Solutions
Mar 9, 2023
The failback could be improved. It should be more intuitive.
EG
AWS Solution Engineer at a tech services company with 51-200 employees
Apr 11, 2023
I set up a test, deleted the source, and went to fail it back, and it didn't work.