AWS Elastic Disaster Recovery offers valuable features like database replication, seamless integration, automated orchestration, and instant block verification. Its cost-effectiveness, ease of use, and scalability are highlighted. Users appreciate the native service's stability, reliability, and managed infrastructure, reducing management time. Seamless integration with AWS services like Route 53 enhances disaster recovery. Pay-as-you-go pricing is advantageous when conducting disaster recovery drills, offering flexibility and reducing potential security breaches compared to competitors.
- "I appreciate the automated orchestration of recovery processes in this solution, especially integration with Route 53 and automatically using Route 53 to switch to a different region directly."
- "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."
AWS Elastic Disaster Recovery requires improved automation and enhanced logging for easier diagnostics. Users face difficulties with archival processes and require more intuitive failback functionality. Customer support and UI could be better. Costs are perceived as high, and more AI-driven automation with security features would be beneficial. Reducing failover and failback time, streamlining data replication, and providing comprehensive network configuration tools could enhance overall user satisfaction.
- "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."