Which solution will meet these requirements MOST cost-effectively?
Set up an Aurora global database and DynamoDB global tables to replicate the databases to a secondary AWS Region. In the primary Region and in the secondary Region, configure an API Gateway API with a Regional endpoint. Implement Amazon CloudFront with origin failover to route traffic to the secondary Region during a DR scenario.
Use AWS Database Migration Service (AWS DMS), Amazon EventBridge (Amazon CloudWatch Events), and AWS Lambda to replicate the Aurora databases to a secondary AWS Region. Use DynamoDB Streams, EventBridge (CloudWatch Events), and Lambda to replicate the DynamoDB databases to the secondary Region. In the primary Region and in the secondary Region, configure an API Gateway API with a Regional endpoint. Implement Amazon Route 53 failover routing to switch traffic from the primary Region to the secondary Region.
Use AWS Backup to create backups of the Aurora databases and the DynamoDB databases in a secondary AWS Region. In the primary Region and in the secondary Region, configure an API Gateway API with a Regional endpoint. Implement Amazon Route 53 failover routing to switch traffic from the primary Region to the secondary Region.
Set up an Aurora global database and DynamoDB global tables to replicate the databases to a secondary AWS Region. In the primary Region and in the secondary Region, configure an API Gateway API with a Regional endpoint. Implement Amazon Route 53 failover routing to switch traffic from the primary Region to the secondary Region.
Explanations:
While Aurora global databases and DynamoDB global tables can provide replication to a secondary AWS Region, using a CloudFront origin failover introduces additional complexity and cost. The solution doesn’t explicitly ensure meeting the RPO and RTO requirements since it relies on CloudFront configuration which may not guarantee quick failover within the specified time.
This solution utilizes AWS DMS and Lambda for replication, which can be complex and may not meet the 2-hour RPO effectively since it relies on event-driven replication rather than synchronous. It also does not inherently provide an efficient RTO, as switching traffic using Route 53 may introduce delays compared to more direct replication methods.
Using AWS Backup to create regular backups in a secondary region is a straightforward solution that meets the RPO and RTO requirements. Backups can be scheduled every hour (meeting the 2-hour RPO), and restoring these backups can typically be accomplished within the 4-hour RTO, making it a cost-effective option.
Setting up Aurora global databases and DynamoDB global tables is a robust solution for real-time data replication and could meet RPO requirements; however, it is more expensive than using AWS Backup and may not be necessary for a 2-hour RPO. Additionally, Route 53 failover routing could add complexity and potential delay in the RTO process.
I estimate that the answer is:
Use AWS Backup to create backups of the Aurora databases and the DynamoDB databases in a secondary AWS Region. In the primary Region and in the secondary Region, configure an API Gateway API with a Regional endpoint. Implement Amazon Route 53 failover routing to switch traffic from the primary Region to the secondary Region.