AWS Elastic Disaster Recovery offers valuable features like easy data replication between clouds, ensuring freedom from vendor lock-in. Its speedy setup, reliability, scalability, and cost-effectiveness with pay-as-you-go pricing are appreciated. Instant block replication is vital for critical workloads. Users benefit from seamless integration with AWS services, reducing infrastructure management time. The managed service offers high availability, security, and flexibility, excelling in backing up and restoring data efficiently. Stability and ease of use enhance its appeal.
- "What I like about ECR AWS is that it is a fully managed service, so I don't need to manage the underlying infrastructure or worry about scalability in AWS concerning building, maintenance, security, and high availability."
- "It offers seamless integration with services like ACL, EKS, and Fargate for deploying containerized applications."
- "Customer service is quite helpful."
AWS Elastic Disaster Recovery needs improvements in automation and ease of use, especially for replicating and utilizing data. Users report outdated data due to complex manual processes and insufficient notifications when servers lag. Many experience issues with logging, requiring reliance on vendor support. The UI could be enhanced, as well as support for handling large archives. Cost, pricing structure, and features like failback and orchestration capabilities are also concerns for users seeking better efficiency and intuitive use.
- "In its current state, ECL integrates with CloudWatch for basic logging and monitoring, yet improvements could include more detailed logs for specific actions, like when I perform actions such as push or pull."
- "An improved AWS pricing model is needed."
- "Since I have to view everything on the console, the previous application solutions like IBM and Sanavi showed the RPO and RTO status directly. In AWS Disaster Recovery Service, these details are not available, making it difficult to check my replication status."