Special Zones: Local Zones & Wavelength

Standard Regions cover most use cases, but some applications need compute infrastructure physically closer to a specific city or network. AWS addresses this with two specialized deployment options.

Local Zones (The City Extension)

A Local Zone is an extension of an AWS Region placed in a specific metropolitan area that doesn't have a full Region. It runs a subset of AWS services (EC2, EBS, ECS, RDS) but is managed as part of its parent Region.

• Example: us-west-2-lax-1a is a Local Zone in Los Angeles, attached to the Oregon Region (us-west-2). Your EC2 instances in this Local Zone are managed through the us-west-2 console and APIs, but the physical hardware is in Los Angeles.
• Latency benefit: A user in Los Angeles connecting to a server in us-west-2-lax-1a experiences single-digit millisecond latency instead of the ~20ms round-trip to Oregon.
• Use cases: Real-time gaming servers, live video production, financial trading platforms, and hybrid cloud migrations where you need AWS compute physically adjacent to an on-premises data center.
• Limitation: Local Zones offer a subset of services. You can't run every AWS service there — check availability before designing an architecture that depends on one.

Wavelength Zones (The 5G Edge)

A Wavelength Zone places AWS compute and storage hardware directly inside a telecommunications provider's 5G network infrastructure (partners include Verizon, Vodafone, KDDI, and SK Telecom).

• The key insight: Traffic from a 5G mobile device reaches the Wavelength Zone server without ever traversing the public internet. The data stays entirely within the carrier's network, eliminating the latency introduced by internet routing.
• Latency: This achieves ultra-low latency — often under 10ms — for mobile-connected devices.
• Use cases: Autonomous vehicles that need real-time map updates, augmented reality (AR) applications, industrial IoT sensors on factory floors connected via 5G, and live sports broadcasting from mobile cameras.
• Architecture: A Wavelength Zone is connected back to its parent AWS Region via a private link, so your Wavelength workloads can still access full AWS services (S3, DynamoDB, etc.) in the parent Region.