An application frequently reads a database in another Region.
Retain high availability while controlling transfer volume and latency.
Choose TWO considerations to confirm first.
Measure cross-Region data volume and review the geographic placement of users and data before selecting the topology.
Detailed explanation
This can create unnecessary transfer charges without validating the requirement.
This can create unnecessary transfer charges without validating the requirement.
Placing workloads closer to users can reduce transfer distance and latency.
Placing workloads closer to users can reduce transfer distance and latency.
DNS caching does not eliminate database data transfer.
DNS caching does not eliminate database data transfer.
Transfer volume directly affects cost and helps estimate latency impact.
Transfer volume directly affects cost and helps estimate latency impact.
Check official documentation
Compare the following points with the official documentation.
AWS data transfer pricingとリージョン設計の公式説明を確認する。
What to confirm
転送量と地理配置をコスト見積もりへ含められる。
Key points
- Cross-Region transfer
- Data-transfer volume
- Geographic placement
Notes
- Environment: AWS公式料金・Well-Architectedドキュメントの確認
- Confirm current AWS service behavior and pricing in the official documentation.
Foundation review
Cost and latency
Transfer volume affects cost while geographic distance influences latency and topology choices.
Availability trade-off
Cross-Region redundancy can improve resilience but must be weighed against transfer and synchronization costs.