Which solution will meet these requirements?
Use Aurora MySQL with the primary DB cluster in us-west-2 and a cross-Region Aurora Replica in eu-west-1
Use Aurora MySQL with the primary DB cluster in us-west-2 and binlog-based external replication to eu-west-1
Use an Aurora MySQL global database with the primary DB cluster in us-west-2 and the secondary DB cluster in eu-west-1
Use Aurora MySQL with the primary DB cluster in us-west-2. Use AWS Database Migration Service (AWS DMS) change data capture (GDC) replication to the secondary DB cluster in eu-west-1
Explanations:
Aurora MySQL cross-Region replicas are asynchronous, and while they can replicate from the primary cluster in us-west-2 to a replica in eu-west-1, the RPO (Recovery Point Objective) would not meet the requirement of a few seconds.
Binlog-based external replication is asynchronous and does not meet the strict RPO requirement of a few seconds for disaster recovery. It also requires more manual management and is less reliable for fast failover.
Aurora MySQL global databases provide cross-Region replication with low-latency, near-real-time data replication between regions. This solution meets the RPO of a few seconds and ensures the database is available in the eu-west-1 Region for disaster recovery.
AWS DMS with change data capture (CDC) would not provide the low-latency replication required for an RPO of a few seconds. It is designed for database migrations, not high-availability disaster recovery.
From what I’ve heard, the answer is:
Use an Aurora MySQL global database with the primary DB cluster in us-west-2 and the secondary DB cluster in eu-west-1
I scheme that the answer is:
Use an Aurora MySQL global database with the primary DB cluster in us-west-2 and the secondary DB cluster in eu-west-1