What are AWS Local Zones?
AWS Local Zones are AWS infrastructure that brings core services to additional metro areas. Each Local Zone is attached to a parent AWS Region and lets you run latency-sensitive applications closer to end users while addressing data residency requirements.
AWS names 30+ metro areas across six continents. In Germany, the Hamburg Local Zone (eu-central-1-ham-1a) is available, with Europe (Frankfurt) as its parent Region.
Core Features
- Extension of an AWS Region: Every Local Zone is attached to a parent Region; control plane operations such as API calls are handled by the parent zone
- Core services on site: Compute, storage, networking, analytics, AI/ML, and databases, including Amazon EC2, Amazon Bedrock, and Amazon SageMaker
- Location-bound data handling: Processing and storage at the site of the respective Local Zone
- Flexible billing: On-Demand, Savings Plans, and Spot
- Per-account opt-in: Local Zones are enabled per AWS account, for example through the EC2 Global View console
- Defined instance selection: Each Local Zone supports a subset of the available EC2 instance types
Typical Use Cases
Latency-sensitive interactive applications: Gaming, AR/VR, and live streaming benefit from the shorter distance between application and end user.
Data residency in regulated industries: Workloads stay at the Local Zone site, for example in Hamburg instead of Frankfurt.
AI inference and training: AWS names inference and training as a use case for Local Zones, including GPU capacity.
Hybrid migration: Applications move from on-premises data centers into a nearby Local Zone step by step while remaining connected to the parent Region.
Benefits
- Hamburg as a German alternative or complement to the Frankfurt Region
- The same APIs and tools as an AWS Region
- Usage-based billing with On-Demand, Savings Plans, and Spot
- 30+ locations worldwide, six of them in Europe
- Connectivity to the full service portfolio of the parent Region
Integration with innFactory
As an AWS Reseller, innFactory supports you with AWS Local Zones: assessing latency and data residency requirements, selecting the right location, designing network architecture between the Local Zone and its parent Region, and operating the workloads placed there.
Typical Use Cases
Frequently Asked Questions
Is there an AWS Local Zone in Germany?
Yes. The Germany (Hamburg) Local Zone is named eu-central-1-ham-1a with zone ID euc1-ham1-az1 and network border group eu-central-1-ham-1. Its parent Region is Europe (Frankfurt), eu-central-1.
Which other Local Zones exist in Europe?
The AWS documentation lists Denmark (Copenhagen, eu-north-1-cph-1a), Finland (Helsinki, eu-north-1-hel-1a), Germany (Hamburg, eu-central-1-ham-1a), Greece (Athens, eu-central-1-ath-1a), Poland (Warsaw, eu-central-1-waw-1a), and Turkey (Istanbul, eu-central-1-ist-1a) for Europe.
Which services are available in a Local Zone?
AWS names core offerings across compute, storage, networking, analytics, AI/ML, and databases, including Amazon EC2, Amazon Bedrock, and Amazon SageMaker. Each Local Zone supports only a subset of the available instance types; check the scope per location in the official documentation.
How are Local Zones billed?
Usage is billed on consumption. AWS names On-Demand, Savings Plans, and Spot as billing options. Actual prices are zone-specific.
How do I enable a Local Zone?
Local Zones must be opted into per AWS account. AWS points to the EC2 Global View console for this. The CLI command aws ec2 describe-availability-zones with the filter zone-type=local-zone lists the Local Zones available to your account.
Note: All product information on this page has been compiled with care, but is provided without guarantee and may be outdated or incomplete. Cloud services evolve rapidly — features, pricing, SLAs, and availability change frequently. Authoritative and up-to-date information can only be found on the official product page of AWS (official documentation). This page does not represent an offer by AWS.