AWS Global Infrastructure: Comprehensive Curriculum Guide

This curriculum provides a structured path for mastering the architectural foundation of the Amazon Web Services (AWS) cloud. Understanding the global footprint is essential for designing resilient, low-latency, and compliant cloud solutions.

## Prerequisites

Before beginning this curriculum, students should possess the following foundational knowledge:

• Basic Cloud Literacy: Understanding of the "cloud" vs. on-premises data centers.
• Networking Fundamentals: Basic knowledge of IP addresses, DNS, and the concept of Latency (the delay between a user's action and a web application's response).
• Internet Infrastructure: Awareness that the internet relies on physical hardware (servers, cables, power grids) located in specific geographic spots.

---

## Module Breakdown

---

## Module Objectives

Module 1: The Core Foundations

• Define a Region: Explain that a Region is a physical location around the world where AWS clusters data centers.
  • Example: US East (N. Virginia) vs. Europe (Ireland).
• Understand Availability Zones (AZs): Describe AZs as one or more discrete data centers with redundant power, networking, and connectivity within a Region.
• Relationship Mapping: Articulate why AZs are physically separated (usually by miles) to prevent synchronized failures from natural disasters.

Module 2: Edge & Specialized Networking

• Define Edge Locations: Explain how these sites store cached versions of data closer to users via Amazon CloudFront.
• Differentiate Local & Wavelength Zones:
  • Local Zones: Bringing compute/storage to specific metro areas (e.g., Chicago) for sub-10ms latency.
  • Wavelength Zones: Embedding AWS services within 5G carrier networks for ultra-low latency mobile apps.

Module 3: Global vs. Regional Services

• Categorize Services: Identify which services operate globally vs. those tied to a specific region.

[!NOTE] Service Scoping: Most AWS services (like EC2) are Regional. However, IAM (Identity and Access Management) and Route 53 (DNS) are Global. S3 is technically global but stores data in a selected Region.

Module 4: Designing for Resilience

• Eliminate Single Points of Failure: Learn to deploy applications across multiple AZs.
• High Availability (HA) Tools: Understand how Elastic Load Balancing (ELB) and Auto Scaling utilize the global infrastructure to maintain uptime.

---

## Visual Anchors

Hierarchy of AWS Infrastructure

Visualizing High Availability

---

## Success Metrics

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

1. Selection Logic: Correctly choose a Region based on Data Sovereignty (legal requirements to keep data in a country), Proximity (latency), and Feature Availability.
2. Architecture Validation: Diagram a web application that remains functional if one entire Availability Zone goes offline.
3. Terminology Distinction: Explain the difference between an AZ (hosting servers) and an Edge Location (caching content).
4. Mathematical Latency Rule: Understand the relationship between distance and speed: $Latency \approx \frac{Distance}{Speed\ of\ Light\ (Fiber)}$
   • Note: Reducing distance via Edge Locations is the primary way to reduce latency.

---

## Real-World Application

Case Study: Global Video Streaming

A streaming company uses the AWS Global Infrastructure to provide a seamless experience:

• The Content (S3): Movies are stored in an S3 bucket in the us-east-1 Region for cost-efficiency.
• The Delivery (CloudFront): When a user in Tokyo watches a movie, the content is cached at a Tokyo Edge Location. This ensures the user doesn't have to wait for data to travel across the Pacific Ocean.
• The Login (IAM): Because IAM is a Global Service, the same user credentials work regardless of which Region the application is accessed from.
• The Reliability: By using Multiple Regions, the company ensures that even if an entire geographic area suffers a massive power outage, users can be redirected to a different continent's infrastructure automatically.

[!TIP] Always design with the "Blast Radius" in mind. By isolating resources into different AZs, you ensure that a fire in one data center doesn't take down your entire business.