Users in a particular city need lower-latency compute than a distant Region can provide.
Choose an AWS global infrastructure location.
Which option should be considered?
AWS Local Zones extend selected compute resources closer to large population centers for latency-sensitive workloads.
Detailed explanation
A single AZ does not necessarily place compute near the users.
A single AZ does not necessarily place compute near the users.
Artifact provides compliance documents and does not provide compute proximity.
Artifact provides compliance documents and does not provide compute proximity.
Local Zones place supported resources closer to users than the parent Region.
Local Zones place supported resources closer to users than the parent Region.
IAM groups control permissions and do not change network distance.
IAM groups control permissions and do not change network distance.
Check official documentation
Compare the following points with the official documentation.
AWS Regions and Availability Zones User GuideのLocal Zonesの説明を確認する。
What to confirm
利用者に近いLocal Zoneの利用可否、対応サービス、料金、データ要件を比較できる。
Key points
- Local Zones
- Low latency
- End user
Notes
- Environment: AWS公式Global Infrastructureドキュメントの確認
- AWS global infrastructure and service availability can change; verify current details in official AWS documentation.
Foundation review
Benefit versus implementation
Agility and elasticity describe cloud capabilities; a particular Region or AZ is an implementation choice that must satisfy other constraints.
Availability and proximity
Use multiple AZs for failure isolation and suitable Regions or Local Zones for geographic proximity and latency.