Curriculum Overview: AWS Global Infrastructure Foundations

This curriculum provides a structured path to understanding how Amazon Web Services (AWS) organizes its physical and networking hardware. Mastery of these concepts is essential for designing resilient, high-performing applications.

Prerequisites

• Cloud Fundamentals: Basic understanding of cloud vs. on-premises computing.
• Networking Basics: Familiarity with IP addressing, DNS, and the concept of latency.
• Virtualization: Awareness of how virtual servers (EC2) use physical hardware.

Module Breakdown

Module Objectives

• Contrast Regions vs. AZs: Explain how Regions provide geographic isolation while AZs provide high availability within a Region.
• Design for Resilience: Use multiple AZs to achieve a fault-tolerant architecture (99.99% availability).
• Optimize Global Latency: Identify how Edge Locations and CloudFront cache data closer to end-users.
• Navigate Compliance: Select Regions based on data sovereignty requirements (e.g., GDPR in EU Regions).

Success Metrics

• Scenario Design: Students must architect a solution that survives the failure of two data centers within one Region.
• Component Mapping: Correctly identify whether to use an Edge Location, Local Zone, or Region for 5 different business use cases.
• Terminology Mastery: Pass a cumulative exam with 90% or higher on global infrastructure questions.
• Latency Calculation: Demonstrate the reduction in Round Trip Time (RTT) when using CloudFront caching.

Global Infrastructure Hierarchy

Real-World Application

• Banking Compliance: A bank uses the EU (Paris) Region (eu-west-3) to ensure customer data never leaves French territory, satisfying national regulations.
• Video Streaming: A media company uses Edge Locations in London to serve high-definition video to UK users, preventing buffering by avoiding a trans-Atlantic data fetch from a US-based origin.
• Disaster Recovery: A tech firm replicates its database across two Regions (e.g., us-east-1 and us-west-2) so that even a massive regional power grid failure does not stop their service.

Examples & Comparisons

Comparison: Deployment Scopes

Infrastructure Visualized

[!IMPORTANT] Availability Zones are designed as independent failure domains. They are physically separated within a metropolitan area to ensure that a flood or fire in one AZ does not affect others.

[!TIP] For the exam, remember: CloudFront always uses Edge Locations, not AZs, to deliver content to users.

High Availability Formula\nBy deploying across $n Availability Zones, where each zone has a failure probability of p$, the probability of total system failure is:

$P(failure) = p^n$\nTherefore, availability is calculated as: $Availability = 1 - p^n$\nExample: If one AZ is 99% reliable ($p=0.01$), using 2 AZs results in $1 - (0.01)^2 = 0.9999$ or 99.99% uptime.

Checkpoint Questions

1. How many data centers are in an Availability Zone? (Answer: At least one or more).
2. Which service uses Edge Locations to reduce latency? (Answer: Amazon CloudFront).
3. What is the primary reason to use multiple Regions? (Answer: Disaster recovery and data sovereignty).