Global users read Aurora data near their locations.
Write in a primary Region and provide low-latency reads from another Region.
Which choice is most appropriate?
Use Aurora Global Database to replicate data across Regions and serve reads from secondary Regions.
Detailed explanation
Aurora Global Database replicates data across Regions and provides read endpoints in secondary Regions.
Aurora Global Database replicates data across Regions and provides read endpoints in secondary Regions.
This retains geographic latency and dependence on one Region.
This retains geographic latency and dependence on one Region.
DNS TTL controls caching and does not replicate database data.
DNS TTL controls caching and does not replicate database data.
S3 replication does not provide an Aurora database or SQL endpoint.
S3 replication does not provide an Aurora database or SQL endpoint.
Check official documentation
Compare the following points with the official documentation.
Amazon Aurora Global Databaseの公式説明を確認する。
What to confirm
リージョン間レプリケーションと読み取り配置をAurora Global Databaseへ対応付けられる。
Key points
- Aurora Global Database
- Secondary Region
- Read latency
Notes
- Environment: AWS公式Auroraドキュメントの確認
- Confirm current AWS service behavior in the official documentation.
Foundation review
Write and read topology
A primary Region can accept writes while secondary Regions serve local reads.
Replication versus DNS
DNS routing chooses an endpoint; it does not copy database records.