AWS Local Zones are a type of AWS infrastructure deployment that place compute, storage, database, and other select services closer to large population, industry, and IT centers, enabling you to deliver applications that require single-digit millisecond latency to end-users.
AWS Services
You can use AWS Local Zones to run various AWS services such as Amazon Elastic Compute Cloud, Amazon Virtual Private Cloud, Amazon Elastic Block Store, Amazon FSx, Amazon Elastic Load Balancing, Amazon EMR, Amazon ElastiCache and Amazon Relational Database Service in geographic proximity to your end users, with more services to be added in the future. You can also use On-Demand Capacity Reservation to reserve capacity for your Amazon EC2 instances in a specific Local Zone. You can enable Local Zones without any additional fees. You pay only for the services you consume in Local Zones.
The table below lists services available in each of the AWS Local Zones. Enable access to the following Local Zones in your Amazon EC2 console.
AWS Local Zones location |
Zone name |
Amazon EC2 | Amazon EBS |
AWS Shield | Amazon ELB | Amazon ECS | Amazon EKS | Amazon VPC |
Amazon Direct Connect | Amazon FSx | Amazon EMR | Amazon ElastiCache | Amazon RDS |
Amazon GameLift | Application Migration Service | NAT Gateway |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Atlanta, US |
us-east-1-atl-1a |
T3, C5d, R5d, and G4dn instances |
General Purpose SSD (gp2) | Standard | ALB | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | |||||
Boston, US |
us-east-1-bos-1a |
T3, C5d, R5d, and G4dn instances | General Purpose SSD (gp2) | Standard | ALB | ✔ | ✔ | ✔ | ✔ | ✔ | ||||||
Chicago, US |
us-east-1-chi-1a |
T3, C5d, R5d, and G4dn instances | General Purpose SSD (gp2) | Standard | ALB | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | |||||
Dallas, US |
us-east-1-dfw-1a |
T3, C5d, R5d, and G4dn instances | General Purpose SSD (gp2) | Standard | ALB | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | |||||
Denver, US |
us-west-2-den-1a |
T3, C5d, R5d, and G4dn instances | General Purpose SSD (gp2) | Standard | ALB | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | |||||
Houston, US |
us-east-1-iah-1a |
T3, C5d, R5d, and G4dn instances | General Purpose SSD (gp2) | Standard | ALB | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | |||||
Kansas City, US |
us-east-1-mci-1a |
T3, C5d, R5d, and G4dn instances | General Purpose SSD (gp2) | Standard | ALB | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | |||||
Las Vegas, US |
us-west-2-las-1a |
T3, C5d, R5d, and G4dn instances | General Purpose SSD (gp2) | Standard | ALB | ✔ | ✔ | ✔ | ✔ | ✔ | ||||||
Los Angeles, US | us-west-2-lax-1a | T3, C5, C5d, M5, R5, R5d, G4dn, G5, and I3en instances | General Purpose SSD (gp3), General Purpose SSD (gp2) Provisioned IOPS SSD (io1), Throughput Optimized HDD (st1), and Cold HDD (sc1) |
Standard |
ALB | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
Los Angeles, US |
us-west-2-lax-1b |
T3, C5, C5d, M5, R5, R5d, G4dn, and I3en instances
|
General Purpose SSD (gp3), General Purpose SSD (gp2) Provisioned IOPS SSD (io1), Throughput Optimized HDD (st1), and Cold HDD (sc1) |
Standard |
ALB | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | |
Miami, US |
us-east-1-mia-1a |
T3, C5d, R5d, G4dn, and M5 instances | General Purpose SSD (gp2) | Standard | ALB | ✔ | ✔ | ✔ | ✔ | ✔ | ||||||
Minneapolis, US |
us-east-1-msp-1a |
T3, C5d, R5d, and G4dn instances | General Purpose SSD (gp2) | Standard | ALB | ✔ | ✔ | ✔ | ✔ | ✔ | ||||||
New York (located in New Jersey), US |
us-east-1-nyc-1a |
T3, C5d, R5d, and G4dn instances | General Purpose SSD (gp2) | Standard | ALB | ✔ | ✔ | ✔ | ✔ | ✔ | ||||||
Philadelphia, US |
us-east-1-phl-1a |
T3, C5d, R5d, and G4dn instances | General Purpose SSD (gp2) | Standard | ALB | ✔ | ✔ | ✔ | ✔ | ✔ | ||||||
Phoenix, US |
us-west-2-phx-2a |
C6i, M6i, R6i, and C6gn instances | General Purpose SSD (gp3), General Purpose SSD (gp2) Provisioned IOPS SSD (io1), Throughput Optimized HDD (st1), and Cold HDD (sc1) | Standard | ALB | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | |||||
Portland, US |
us-west-2-pdx-1a |
T3, C5d, R5d, and G4dn instances | General Purpose SSD (gp2) | Standard | ALB | ✔ | ✔ | ✔ | ✔ | ✔ | ||||||
Seattle, US |
us-west-2-sea-1a |
T3, C5d, R5d, and G4dn instances |
General Purpose SSD (gp2) | Standard | ALB | ✔ | ✔ | ✔ | ✔ | ✔ | ||||||
Auckland, New Zealand |
ap-southeast-2-akl-1a |
T3, C5, R5, G4dn, and M5 instances | General Purpose SSD (gp2) | Standard | ✔ | ✔ | ✔ | ✔ | ||||||||
Bangkok, Thailand |
ap-southeast-1-bkk-1a |
T3, C5, R5, G4dn, and M5 instances | General Purpose SSD (gp2) | Standard | ✔ | ✔ | ✔ | ✔ | ||||||||
Buenos Aires, Argentina |
us-east-1-bue-1a |
T3, C5, R5, G4dn, and M5 instances | General Purpose SSD (gp2) | Standard | ✔ | ✔ | ✔ | ✔ | ||||||||
Copenhagen, Denmark |
eu-north-1-cph-1a |
T3, C5, R5, G4dn, and M5 instances | General Purpose SSD (gp2) | Standard | ✔ | ✔ | ✔ | ✔ | ||||||||
Delhi, India |
ap-south-1-del-1a |
T3, C5, R5, G4dn, and M5 instances | General Purpose SSD (gp2) | Standard | ✔ | ✔ | ✔ | ✔ | ||||||||
Hamburg, Germany |
eu-central-1-ham-1a |
T3, C5, R5, G4dn, and M5 instances | General Purpose SSD (gp2) | Standard | ✔ | ✔ | ✔ | ✔ | ||||||||
Helsinki, Finland |
eu-north-1-hel-1a |
T3, C5, R5, G4dn, and M5 instances | General Purpose SSD (gp2) | Standard | ✔ | ✔ | ✔ | ✔ | ||||||||
Kolkata, India |
ap-south-1-ccu-1a |
T3, C5, R5, G4dn, and M5 instances | General Purpose SSD (gp2) | Standard | ✔ | ✔ | ✔ | ✔ | ||||||||
Lagos, Nigeria |
af-south-1-los-1a |
T3, C5, R5, G4dn, and M5 instances | General Purpose SSD (gp2) | Standard | ✔ | ✔ | ✔ | ✔ | ||||||||
Lima, Peru |
us-east-1-lim-1a |
T3, C5, R5, G4dn, and M5 instances | General Purpose SSD (gp2) | Standard | ✔ | ✔ | ✔ | ✔ | ||||||||
Manila, Philippines |
ap-southeast-1-mnl-1a |
T3, C5, R5, G4dn, and M5 instances | General Purpose SSD (gp2) | Standard | ✔ | ✔ | ✔ | ✔ | ||||||||
Muscat, Oman |
me-south-1-mct-1a |
T3, C5, R5, G4dn, and M5 instances | General Purpose SSD (gp2) | Standard | ✔ | ✔ | ✔ | ✔ | ||||||||
Perth, Australia |
ap-southeast-2-per-1a |
T3, C5, R5, G4dn, and M5 instances | General Purpose SSD (gp2) | Standard | ✔ | ✔ | ✔ | ✔ | ||||||||
Querétaro, Mexico |
us-east-1-qro-1a |
T3, C5, R5, G4dn, and M5 instances | General Purpose SSD (gp2) | Standard | ✔ | ✔ | ✔ | ✔ | ||||||||
Santiago, Chile |
us-east-1-scl-1a |
T3, C5, R5, G4dn, and M5 instances | General Purpose SSD (gp2) | Standard | ✔ | ✔ | ✔ | ✔ | ||||||||
Taipei, Taiwan |
ap-northeast-1-tpe-1a |
T3, C5, R5, G4dn, and M5 instances | General Purpose SSD (gp2) |
Standard | ✔ | ✔ | ✔ | ✔ | ||||||||
Warsaw, Poland |
eu-central-1-waw-1a |
T3, C5, R5, G4dn, and M5 instances | General Purpose SSD (gp2) | Standard | ✔ | ✔ | ✔ | ✔ | ||||||||
*Upcoming |
Compute and Storage
AWS Local Zones offer a selection of general purpose, compute optimized, memory optimized, accelerated computing, and storage optimized Amazon Elastic Compute Cloud (EC2) instance families (including T3, C5, M5, R5, R5d, I3en, G4) as well as Amazon Elastic Block Store (EBS) volumes such as General Purpose SSD (gp3), General Purpose SSD (gp2), Provisioned IOPS SSD (io1), Throughput Optimized HDD (st1), and Cold HDD (sc1) for persistent local block storage. AWS Local Zones also offers two file services locally: Amazon FSx for Lustre (a high-performance POSIX file system) and AWS FSx for Windows File Server (native Microsoft Windows file system).
Containers
You can run Kubernetes pods in the Local Zones as part of your Amazon Elastic Kubernetes Service clusters. You can also run Amazon Elastic Container Service tasks in the Local Zones.
Networking
Seamlessly extend Amazon Virtual Private Cloud (VPC) in an account to span across Availability Zones and AWS Local Zones. You can create a subnet in your regional VPC and associate it with a Local Zone just as you associate subnets with an Availability Zone in an AWS Region to extend all VPC features including Security Groups, Network ACLs, and Route Tables to a Local Zone.
Internet & Direct Connect
Local Zones have local internet ingress and egress to reduce latency. Local Zones also support AWS Direct Connect, giving you the opportunity to route your traffic over a private network connection.
Access Regional Services
AWS Local Zones allow you to seamlessly connect to the full range of services in the AWS Region such as Amazon S3 and DynamoDB through the same APIs and tool sets over AWS’s private and high bandwidth network backbone.
AWS Tools
AWS tools such as AWS CloudFormation, Amazon CloudWatch, AWS CloudTrail, and others can be used to run and manage workloads as they do for Cloud workloads today.