A company’s database runs on an Amazon RDS for MySQL DB instance in us-east-1. They must make the same data available to customers in Europe with minimal latency and no stale data. Both US and European customers must be able to write, and writes made by one region must be visible in the other in real time. Which solution will satisfy these requirements?

The correct solution leverages Amazon Aurora Global Database with write forwarding, which is designed for low-latency global reads and writes with near real-time data synchronization. Converting the existing RDS for MySQL to Aurora is a necessary first step. Creating an Aurora read replica, promoting it, and then adding a secondary region with write forwarding allows for multi-region active-active write capabilities, ensuring writes in one region are immediately visible in others. Incorrect options: Adding a cross-Region replica for RDS for MySQL does not support active-active writes directly back to the primary in a performant way, and RDS for MySQL replicas are typically read-only. Copying snapshots and using MySQL logical replication is complex to manage, can have higher latency, and does not inherently support active-active writes with real-time consistency and write forwarding like Aurora Global Database. Converting the RDS instance directly to an Aurora DB cluster is a valid step, but the question implies an existing RDS instance that needs to be migrated, and the provided correct answer details the full migration path including the replica creation and promotion. The key is the write forwarding capability of Aurora Global Database.