Curriculum Overview: AWS Global Infrastructure Foundations

This curriculum provides a comprehensive breakdown of the AWS Global Infrastructure, focusing on the architectural relationships between Regions, Availability Zones (AZs), and Edge Locations. Mastery of these concepts is essential for designing resilient, high-performing, and cost-effective cloud solutions.

Prerequisites

Before starting this module, students should have a baseline understanding of the following:

• Basic Cloud Concepts: Understanding of what cloud computing is (on-demand delivery of IT resources).
• AWS Management Console: Familiarity with navigating the primary AWS web interface.
• Networking Fundamentals: Basic knowledge of IP addresses, latency, and data transfer.

Module Breakdown

Learning Objectives per Module

Module 1: AWS Regions

• Define an AWS Region as a physical location around the world where AWS clusters data centers.
• Explain the criteria for selecting a Region: Data Sovereignty, Latency, Pricing, and Service Availability.
• Differentiate between standard regions and restricted regions like GovCloud.

Module 2: Availability Zones (AZs)

• Describe an AZ as one or more discrete data centers with redundant power, networking, and connectivity.
• Explain the relationship: A Region consists of at least two AZs (often three or more).
• Analyze how AZs act as independent failure domains, separated physically to mitigate localized disasters.

Module 3: Edge Locations

• Identify Edge Locations as sites used by Amazon CloudFront to cache content closer to end users.
• Compare Edge Locations to AZs: Edge Locations are for content delivery, while AZs are for resource hosting.

Examples Section

[!TIP] Real-World Scenario: Designing for Resilience

• Single AZ Deployment: If you host an EC2 instance in one AZ and that AZ loses power, your app goes down.
• Multi-AZ Deployment: You host instances in AZ-A and AZ-B. If AZ-A fails, traffic automatically routes to AZ-B. This is High Availability.
• Multi-Region Deployment: You host your app in us-east-1 (Virginia) and eu-west-1 (Ireland). If an entire geographic region faces a massive outage, you failover to the other continent. This is Disaster Recovery.

Comparison of Infrastructure Components

Success Metrics

To demonstrate mastery of this curriculum, students must be able to:

1. Diagram the Hierarchy: Correctly place Data Centers within AZs and AZs within Regions.
2. Explain Isolation: Articulate why AZs are physically separated (typically by miles) but logically connected.
3. Identify Endpoints: Correctly format a service endpoint (e.g., service.region.amazonaws.com).
4. Select Infrastructure: Given a business requirement (e.g., "Must keep data in Germany"), select the appropriate Region.

Real-World Application

Understanding this hierarchy is the foundation of the AWS Certified Cloud Practitioner exam and the daily work of a Cloud Architect.

• Cost Optimization: Different Regions have different pricing structures for the same services.
• User Experience: Using Edge Locations ensures a user in Tokyo doesn't wait for data to travel from a server in New York ($Latency \approx \frac{Distance}{Speed \space of \space Light}$).
• Business Continuity: Companies use Multi-AZ architectures to guarantee 99.99% uptime for critical banking or healthcare applications.