This series is intended to be a personal study guide. Information may not be comprehensive or accurate. I am sharing it in case others find it useful. Please feel free to comment if any information is inaccurate.
3.2 Define the AWS global infrastructure
Describe the relationships among Regions, Availability Zones, and Edge Locations
- Regions - physical locations in the world where data centers are clustered; contain multiple AZs
- Availability Zones - one or more discrete data centers with redundant systems
- Edge Locations - site that CloudFront uses to cache copies of content for faster delivery to end users
Describe how to achieve high availability through the use of multiple Availability Zones
-
Recall that high availability is achieved by using multiple AZs
- Using multiple AZs means if one AZ goes offline the data is still available
-
Recognize that AZs do not share single points of failure
- Different AZs do not use the same physical resources and will not fail together
Describe when to consider the use of multiple AWS Regions
- Disaster recovery/business continuity - data and services withstand large-scale disaster events
- Low latency for end-users - deploying in regions close to user bases
- Data sovereignty - different regions may have different regulations regarding data
Describe at a high level the benefits of Edge Locations
-
Amazon CloudFront
- Reduce latency by deploying through globally dispersed Points of Presence
-
AWS Global Accelerator
- Improve network traffic performance using AWS global infrastructure
- Get two global static public IPs to serve as fixed entry point to application
Top comments (0)