
Amazon Web Services (AWS) Regions, Deployment & Data Residency 2026
AWS spans 39 regions and 123 availability zones behind 750+ CloudFront edge points, plus an EU Sovereign Cloud. App Runner reaches only 11 of them.
Amazon Web Services (AWS) Regions & Deployment verdict
AWS carries the largest footprint on the market.
39 regions and 123 Availability Zones, with 2 more regions and 7 more zones announced, fronted by 750+ CloudFront edge points. An EU Sovereign Cloud sits entirely inside the EU for strict sovereignty.
One decision comes first. If you are starting new managed-container work, skip App Runner, since it stops taking new customers on April 30, 2026, so build on ECS Express Mode instead. After that, region choice is easy, because AWS almost certainly has one near your users. For EU residency use Ireland, Frankfurt, London or Paris, or the EU Sovereign Cloud when sovereignty has to be strict. Front any multi-region service with a global load balancer, since each App Runner service lives in one region.
- App Runner stopped taking new customers on April 30, 2026. Use Amazon ECS Express Mode for new managed-container deployments.
- App Runner reaches only 11 of the 39 regions, and each service is regional. Multi-region needs a global load balancer in front.
- There is no dedicated App Runner or Lightsail SLA. The EC2 compute SLA applies instead.
- Regions
- 39
- Availability Zones
- 123
- App Runner regions
- 11
- CloudFront PoPs
- 750+
- EU Sovereign Cloud
- Yes
This page covers where AWS deploys and how residency works. Performance and pricing live on their own pages.
Pick your Amazon Web Services (AWS) region and deployment
14 regions across 5 continents · nearest failover us-east-2 · residency: eu-west-1, eu-west-2, eu-west-3 +2
Create an App Runner service in us-east-1 from an image or source.
aws apprunner create-service \
--region us-east-1 \
--service-name my-app \
--cli-input-json file://input.jsonApp Runner is regional and closed to new customers (use ECS Express Mode); deploy one service per region for multi-region, behind a global load balancer. The nearest region above is a placement hint.
Real Amazon Web Services (AWS) regions and deployment commands. Confirm residency guarantees against your contract.
Deploy AWS: apprunner.yaml and the CLI
For a source-code service, apprunner.yaml defines runtime, build commands (pre-build/build/post-build) and the run command, port and env. CPU and memory are NOT set here, they go through the instance configuration in the API or CLI. Image-based services skip this file.
version: 1.0
runtime: python3
build:
commands:
pre-build:
- yum install openssl
build:
- pip install -r requirements.txt
post-build:
- python manage.py test
env:
- name: DJANGO_SETTINGS_MODULE
value: "django_apprunner.settings"
run:
runtime-version: 3.11
command: python app.py
network:
port: 8000
env:
- name: MY_VAR_EXAMPLE
value: "example"Create the service in a specific region with --region, pointing at an ECR image or a source repo via an input JSON. The instance configuration sets CPU and memory; an auto-scaling configuration ARN attaches reusable scaling settings.
aws apprunner create-service \
--region __REGION__ \
--service-name golang-container-app \
--cli-input-json file://input.json
# input.json (image-based service)
# {
# "ServiceName": "golang-container-app",
# "SourceConfiguration": {
# "ImageRepository": {
# "ImageIdentifier": "123456789012.dkr.ecr.__REGION__.amazonaws.com/golang-app:latest",
# "ImageConfiguration": { "Port": "8080" },
# "ImageRepositoryType": "ECR"
# }
# },
# "InstanceConfiguration": { "Cpu": "1 vCPU", "Memory": "3 GB" }
# }InstanceConfiguration picks the vCPU/memory combo (0.25 to 4 vCPU, 0.5 to 12 GB). Attach a reusable auto-scaling configuration by ARN to control min size, max size and max concurrency across services.
{
"InstanceConfiguration": {
"Cpu": "1 vCPU",
"Memory": "3 GB"
},
"AutoScalingConfigurationArn":
"arn:aws:apprunner:__REGION__:123456789012:autoscalingconfiguration/high-availability/3"
}
# Cpu: 256 | 512 | 1024 | 2048 | 4096 (0.25-4 vCPU)
# Memory: 512 | 1024 | 2048 | 3072 | 4096 | 6144 | 8192 | 10240 | 12288Regions and App Runner availability
| Region code | Location | App Runner | Continent |
|---|---|---|---|
| us-east-1 | N. Virginia, USA | Yes | North America |
| us-east-2 | Ohio, USA | Yes | North America |
| us-west-2 | Oregon, USA | Yes | North America |
| ca-central-1 | Montreal, Canada | No | North America |
| sa-east-1 | Sao Paulo, Brazil | No | South America |
| eu-west-1 | Ireland | Yes | Europe |
| eu-west-2 | London, UK | Yes | Europe |
| eu-west-3 | Paris, France | Yes | Europe |
| eu-central-1 | Frankfurt, Germany | Yes | Europe |
| eu-north-1 | Stockholm, Sweden | No | Europe |
| ap-south-1 | Mumbai, India | Yes | Asia |
| ap-southeast-1 | Singapore | Yes | Asia |
| ap-northeast-1 | Tokyo, Japan | Yes | Asia |
| ap-southeast-2 | Sydney, Australia | Yes | Oceania |
Amazon Web Services (AWS) footprint and region selection
| Aspect | Value | Notes |
|---|---|---|
| Global footprint | 39 regions / 123 AZs | Plus 2 regions and 7 AZs announced |
| App Runner reach | 11 regions | Regional service, one region per service |
| App Runner multi-region | One service per region | Front with a global load balancer / DNS |
| Lightsail reach | 16+ regions | Region chosen at instance creation |
| Edge network | 750+ CloudFront PoPs | 100+ cities, 50+ countries |
| EU Sovereign Cloud | Independent EU cloud | Fully located within the European Union |
Amazon Web Services (AWS) data residency and compliance
| Control | Option | Notes |
|---|---|---|
| EU regions | Ireland, London, Paris, Frankfurt, Stockholm, Milan | App Runner in Ireland, London, Paris, Frankfurt |
| EU Sovereign Cloud | Fully within the EU | Independent cloud for digital sovereignty |
| Global certifications | ISO 27001/17/18/701, SOC 1/2/3 | Plus PCI DSS and CSA STAR |
| US public sector | HIPAA, FedRAMP, FISMA, CJIS | GovRAMP, DoD, IRS 1075 |
| App Runner EU regions | eu-west-1/2/3, eu-central-1 | Ireland, London, Paris, Frankfurt |
What to verify before you commit to Amazon Web Services (AWS)
- App Runner stopped accepting new customers on April 30, 2026, so new managed-container deployments should target Amazon ECS Express Mode instead
- App Runner is a regional service available in only 11 of the 39 regions, so multi-region apps must deploy one service per region behind a global load balancer
- There is no dedicated App Runner or Lightsail SLA; the EC2 compute SLA, 99.99% regional and 99.5% per instance, is the applicable guarantee
- apprunner.yaml only configures source-code services and does not set CPU or memory, which come from the instance configuration via the API or CLI
Amazon Web Services (AWS) Regions & Deployment FAQ
How many regions does AWS have?
The AWS Cloud spans 123 Availability Zones inside 39 geographic regions, the largest footprint of any cloud, with 7 more zones and 2 more regions announced in Saudi Arabia and Chile. App Runner reaches only 11 of those regions. Lightsail covers 16+, while EC2 and CloudFront, at 750+ edge points, cover the whole footprint.
Is App Runner available in my region?
App Runner runs in 11 regions: us-east-1, us-east-2, us-west-2, ap-south-1, ap-southeast-1, ap-southeast-2, ap-northeast-1, eu-central-1, eu-west-1, eu-west-2, eu-west-3. Each service is regional, living in a single region. One thing to note: App Runner stopped accepting new customers on April 30, 2026. ECS Express Mode is the broader successor.
Does AWS support EU data residency?
Extensively. Six EU regions exist: Ireland, London, Paris, Frankfurt, Stockholm, Milan. App Runner supports the first four of those. For strict digital sovereignty, AWS runs an independent European Sovereign Cloud located entirely within the EU. On paper it holds ISO 27001, 27017, 27018, 27701, SOC 1/2/3, PCI DSS, CSA STAR, with GDPR alignment.
How does multi-region work for App Runner?
Not as one service. Each App Runner service runs in a single region behind a region-specific endpoint like apprunner.us-east-1.amazonaws.com. For multi-region you deploy a separate service per region and route between them with a global load balancer or latency-based DNS. It is the standard AWS pattern, but more setup than a platform with built-in multi-region replicas.
How do I deploy and pin a region on App Runner?
For a source-code service, commit an apprunner.yaml with the build and run configuration, then run aws apprunner create-service --region <region> --cli-input-json file://input.json. CPU and memory go in the InstanceConfiguration, not apprunner.yaml. Attach an auto-scaling configuration ARN to set min and max size and concurrency. For anything new, use ECS Express Mode instead.
Sources & verification
| Source | What was checked | Last checked |
|---|---|---|
| Amazon Official | Official product page | July 10, 2026 |
| Amazon About Aws Global Infrastructure | About Aws Global Infrastructure | July 10, 2026 |
| Amazon Cloudfront Features | Cloudfront Features | July 10, 2026 |
| Amazon Compliance Programs | Compliance Programs | July 10, 2026 |
| Amazon Compute Sla | Uptime SLA | July 10, 2026 |
| Amazon Developer docs | Dg Config File Ref | July 10, 2026 |
| Amazon Developer docs | Apprunner Create Service | July 10, 2026 |
Every fact on this Amazon Web Services (AWS) page is tied to a named source and a verification date. Freshness-sensitive figures trace to the sources above; verify against the vendor before relying on them.
Explore Amazon Web Services (AWS)
Every page on Amazon Web Services (AWS) in one place, you are on regions & deployment.
Snapshot, score and verdict
You are here
Latency, throughput, uptime and behaviour under scale
Every tier and the entry price
Compared and ranked vs peers
Price and feature change history
Browse the full Cloud Hosting category
