AWS Local Zones
Definition:
AWS Local Zones are extensions of an AWS Region that place compute, storage, database, and other services physically closer to end users in specific metropolitan areas.
Key Characteristics
- Low-latency access
- Designed for applications that need single-digit millisecond latency to end users in a specific city or metro area.
- Example: Real-time gaming, video streaming, financial trading apps.
- Extension of a parent region
- Each Local Zone is connected to its parent AWS Region (e.g.,
eu-central-1). - You can extend your VPC from the parent region into the Local Zone.
- Supports dynamic compute
- You can run EC2 instances, EKS nodes, RDS, and other services in a Local Zone.
- Unlike CloudFront, Local Zones run actual application compute, not just caching.
- Services available
- EC2, EBS, VPC, RDS, ECS, EKS, and some other services.
- Not every AWS service is available in a Local Zone — it’s focused on low-latency workloads.
Use Cases
| Use Case | Why Local Zones help |
|---|---|
| Real-time gaming | Low latency to players in a city |
| Live video streaming | Encode and process video near users |
| Financial trading apps | Millisecond-level market data processing |
| AR/VR applications | Low latency is critical for immersive experiences |
Analogy
Think of Local Zones like a mini AWS data center in your city:
- Parent region (e.g., Frankfurt
eu-central-1) → main data center - Local Zone (e.g., Berlin) → a “branch office” data center closer to users
- Your VPC spans both → compute runs in Berlin, data stays in Frankfurt
Key Exam Tip
- Dynamic, latency-sensitive apps → AWS Local Zones
- Static content or caching → CloudFront edge locations
AWS Local Zones are used when your application requires extremely low latency for end users in a specific city or metro area. Think of workloads that can’t tolerate the network round-trip time to a full AWS Region.
1. Real-time applications
- Gaming: Multiplayer games where milliseconds matter for player actions.
- Live streaming / broadcasting: Video encoding and processing near viewers.
- AR/VR applications: High interactivity demands single-digit millisecond latency.
2. Financial and trading applications
- Stock trading, high-frequency trading: Local Zones can host compute near stock exchanges to reduce latency.
- Market data processing: Fast ingestion and response times are critical.
3. Hybrid or edge workloads
- On-premises integration: Users in a city can access resources in a Local Zone instead of traveling all the way to the parent region.
- Latency-sensitive data processing: Local preprocessing before sending data to the main region.
4. Software development / testing
- Low-latency testing environments: Developers need to test apps under conditions close to the end user.
- Can be used to mimic real-world latency scenarios for metro-specific deployment.
5. High-performance computing (HPC) near users
- Simulation or rendering workloads: Compute-intensive tasks that need fast interaction with local data sources.
Key Takeaways
- Not for general workloads: If latency is not critical, use the main region.
- Dynamic compute only: CloudFront is for static caching; Local Zones can run EC2, EKS, RDS, etc.
- Best for cities far from your parent region or with strict latency SLAs.
Top comments (0)