What should the DevOps engineer do to resolve this issue?
Create an Amazon DynamoDB table in Europe. Use DynamoDB Accelerator (DAX) to configure replication between the DB cluster and the DynamoDB table. Configure the users’ machines to point to the DynamoDB table in Europe.
Create cross-Region Aurora Replicas in North America, and activate synchronous replication. Configure the users’ machines to point to the Aurora reader endpoint in North America.
Create an Aurora global database. Use the existing DB cluster as the primary cluster, and add a secondary cluster in an AWS Region in Europe. Configure the users’ machines to point to the Aurora reader endpoint in Europe.
Use Amazon DynamoDB global tables in an AWS Region in Europe. Set up continuous replication between the DB cluster and the DynamoDB table by using AWS Database Migration Service (AWS DMS). Configure the users’ machines to point to the DynamoDB table in Europe.
Explanations:
DynamoDB is not designed to replicate PostgreSQL data directly, and DynamoDB Accelerator (DAX) would not resolve the issue for real-time reporting on PostgreSQL data. This option is not suitable.
Cross-Region Aurora Replicas with synchronous replication is not a viable solution because synchronous replication requires low-latency network connections between regions, which could still lead to performance issues.
An Aurora global database allows for low-latency read replicas in different regions. The secondary cluster in Europe would provide up-to-date data with low latency for the analysts, improving report generation performance.
Amazon DynamoDB and AWS Database Migration Service (DMS) are not ideal for real-time reporting on a PostgreSQL database. DMS is typically used for one-time data migrations or asynchronous replication, not for real-time access to PostgreSQL data.