For European Founders Building On AWS

AWS European Region Selection Guide, Pick the Right Region

A practitioner's guide to choosing AWS regions in Europe, by data residency, latency, compliance, and resilience requirements. Updated for 2026 including the AWS European Sovereign Cloud roadmap.

Book Free Region Review →Jump to Decision Matrix

EU Regions · 2026Practitioner Guide

Region selection is the foundation. Get it wrong and everything compounds.

EU Regions

2026

Sovereign Cloud

Decision Factors

Multi-Region Patterns

Most companies pick a region in the first month and live with the consequences for years. We help you pick deliberately.— HAZERCLOUD region selection practice

EU Coverage

8 regions.

Quick Decision Matrix

Pick your region by primary requirement.

Most workloads have one dominant constraint. Start with that, then validate against secondary factors. Real architectures often combine multiple regions, see the multi-region patterns below.

UK GDPR data residency required?

eu-west-2 (London), UK GDPR alignment, post-Brexit independence, ~5ms latency from London

Strict German residency or BaFin/BSI alignment?

eu-central-1 (Frankfurt), densest AWS footprint in EMEA, C5 attestation, BaFin-friendly

French residency or HDS healthcare data?

eu-west-3 (Paris), French residency, HDS hosting eligibility, ACPR/CNIL alignment

Lowest latency to broadest EU customer base?

eu-west-1 (Ireland), most established, deepest service availability, default for non-region-specific workloads

Nordic latency optimization?

eu-north-1 (Stockholm), lowest carbon footprint, strong for Nordic SaaS

Italian residency required?

eu-south-1 (Milan), Italian residency, lowest latency to South Europe and North Africa

Spanish residency required?

eu-south-2 (Spain, Aragón), Spanish residency, low latency to Iberian peninsula

Swiss residency or DSG alignment?

eu-central-2 (Zurich), Swiss residency, FINMA-friendly, strong for DACH compliance

Region-By-Region Detail

AWS regions in Europe, service-by-service.

Every region has different service availability, attestation coverage, and cost profile. Below is the practitioner-grade detail.

eu-west-1 · IRELAND · 2007

Ireland (Dublin)

Most established EU AWS region, comprehensive service availability
Default choice when no specific country residency required
Lowest latency to UK + Western EU customer bases
Most cost-effective for variable workloads
3 AZ + Local Zone (Dublin)
Compliance: ISO 27001/27017/27018, SOC 2/3, PCI DSS, HIPAA-eligible

eu-central-1 · FRANKFURT · 2014

Frankfurt

Densest AWS service availability in EMEA, every major launch
Strong for DACH region (Germany, Austria, Switzerland)
BaFin-friendly with C5 attestation
Local Zone in Hamburg
3 AZ; ~3% premium vs eu-west-1
Compliance: ISO 27001/27017/27018, SOC 2/3, C5, BSI IT-Grundschutz baseline

eu-west-2 · LONDON · 2016

London

UK GDPR data residency, post-Brexit independence
Lowest latency for UK customer base
3 AZ; near-complete service availability
~5% premium vs eu-west-1
Available via UK G-Cloud framework
Compliance: ISO 27001/27017/27018, SOC 2/3, PCI DSS, NHS DSP-aligned, Cyber Essentials Plus

eu-west-3 · PARIS · 2017

Paris

French residency, ACPR-aligned for FinTech
HDS healthcare hosting certification
Service availability strong but slightly behind eu-central-1 for newest services
3 AZ; ~5% premium vs eu-west-1
Does not hold SecNumCloud (use AWS European Sovereign Cloud for sovereign workloads)
Compliance: ISO 27001/27017/27018, SOC 2/3, HDS, PCI DSS

eu-north-1 · STOCKHOLM · 2018

Stockholm

Nordic data residency (Sweden, Finland, Norway, Denmark)
Lowest carbon footprint AWS region globally
Strong service availability but typical newest-service lag of 6-12 months
3 AZ; competitive pricing
Lowest latency to Nordic customer bases
Compliance: ISO 27001/27017/27018, SOC 2/3, PCI DSS

eu-south-1 · MILAN · 2020

Milan

Italian residency, strong for Italian regulated workloads
Lowest latency to South Europe (Italy, Greece, Malta) and North Africa
Service availability: comprehensive but newest services arrive last
3 AZ
Compliance: ISO 27001/27017/27018, SOC 2/3, PCI DSS
Useful for North African market expansion via low-latency hub

eu-south-2 · SPAIN · 2022

Spain (Aragón)

Spanish residency, growing data sovereignty importance
Low latency to Iberian peninsula (Spain, Portugal)
Newest EU region, service availability still growing
3 AZ
Compliance: ISO 27001/27017/27018, SOC 2/3, PCI DSS
Strong for Latin America-bridging workloads

eu-central-2 · ZURICH · 2022

Zurich

Swiss residency, important for FINMA-regulated FinTech
Strong for DACH compliance overlay
Service availability growing; newer region with focused service set
3 AZ
Compliance: ISO 27001/27017/27018, SOC 2/3, FINMA-aligned
~10% premium vs eu-west-1; cost-aware Swiss workloads use as DR not primary

EU City To AWS Region Latency

Latency from major EU cities to AWS regions.

Indicative round-trip latencies. Actual depends on ISP, peering, and TCP/IP stack tuning, but these numbers reflect typical observed performance.

From City	eu-west-1	eu-central-1	eu-west-2	eu-west-3	eu-north-1
London	12ms	15ms	5ms	20ms	35ms
Berlin	22ms	10ms	18ms	15ms	22ms
Paris	18ms	12ms	10ms	5ms	28ms
Amsterdam	12ms	10ms	10ms	12ms	25ms
Madrid	28ms	28ms	25ms	20ms	42ms
Milan	30ms	15ms	25ms	18ms	38ms
Stockholm	35ms	25ms	32ms	30ms	5ms
Dublin	5ms	22ms	15ms	22ms	35ms

Green = under 15ms (excellent for interactive workloads)

Multi-Region Patterns

When does multi-region make sense?

Single-region is enough for most workloads. Multi-region adds operational complexity. Three patterns cover ~95% of real-world EU multi-region needs.

Pattern 01 · Common

DR-Only (Active-Passive)

Primary region handles all traffic
DR region holds backups + warm standby for critical services
RTO typically 4-12 hours; RPO typically 5-15 minutes
Simplest pattern; ~15-25% cost overhead
Suitable for: most SaaS, ISO 27001 baseline, GDPR Article 32 resilience
Common pairs: eu-west-1 + eu-central-1, eu-west-2 + eu-west-1

Pattern 02 · Read-Heavy

Active-Active Read Replicas

Writes go to primary region only
Reads served from local region (lowest latency)
Aurora Global Database, ElastiCache Global Datastore enable this
RTO typically 1-5 minutes for read failover
~30-50% cost overhead; significant ops complexity
Suitable for: read-heavy analytics, content distribution, multi-EU customer bases

Pattern 03 · DORA-Grade

Full Active-Active

Both regions handle production traffic simultaneously
Conflict resolution required at application layer
RTO typically <1 minute; RPO <30 seconds
~80-100% cost overhead; high ops complexity
Suitable for: DORA-grade FinTech resilience, critical financial infrastructure
Required when single-region failure is unacceptable for any duration

2026 And Beyond

AWS European Sovereign Cloud, what you need to know.

Announced 2023, launching late 2025/2026, AWS European Sovereign Cloud is a separate AWS partition operated entirely by EU-resident personnel and EU-incorporated entities. It targets workloads that cannot use standard AWS regions for sovereignty reasons.

What it is

A separate AWS partition (like AWS GovCloud for US government, but for European sovereignty). Independent operations, EU-resident personnel only, EU-incorporated entity.

First region

Brandenburg, Germany, first launch target late 2025 / 2026. Additional regions to follow.

Who needs it

French SecNumCloud requirements · highly-regulated EU government workloads · sovereign-classified defense/aerospace · workloads where US CLOUD Act exposure is unacceptable

Who doesn't

Most European FinTech, SaaS, HealthTech, standard AWS EU regions with proper architecture and Schrems II Transfer Impact Assessments are sufficient. Don't pay the European Sovereign Cloud premium unless your specific regulatory situation demands it.

Service availability

Will start with subset of AWS services; expansion expected over 2026-2028. Most modern services available; some specialized services delayed.

Cost profile

Expected premium of 20-40% over standard AWS EU regions. Verify pricing at launch.

FAQ

Region selection questions European founders ask first.

Have a specific scenario? Book a 30-min call and we'll work through your exact decision factors.

Book Free Region Review →

We're a UK company with EU customers. eu-west-2, eu-west-1, or both?+

Most common answer: both. eu-west-2 (London) for UK GDPR data, eu-west-1 (Ireland) for EU GDPR data. Cross-region replication keeps DR coverage. For very early-stage startups, starting with eu-west-1 only and adding eu-west-2 later is acceptable, UK-residency enforcement is relatively new.

Can we change regions later, or is this a permanent decision?+

Changing primary region is technically possible but operationally painful, typically 6-12 weeks of work to migrate data, applications, DNS, and customer expectations. Cost-wise, AWS data transfer charges between regions add up. Treat the initial choice as a 3-5 year commitment.

What if AWS launches a new region we want to use?+

AWS launches a new EU region every 1-3 years. Most companies don't migrate to new regions reactively, switching is painful enough that you only do it for compelling regulatory or commercial reasons. AWS European Sovereign Cloud (2026+) is the rare exception likely to drive migrations from incumbent regions.

How do we handle multi-region for DORA without doubling our AWS bill?+

Active-passive DR-only typically adds 15-25% to the AWS bill, not the doubling people fear. The trick is intelligent reservation: hot standby for compute, warm standby for stateful services, full standby only for data layer. Most DORA-grade resilience can be achieved without active-active complexity.

Do we need to use Local Zones or Wavelength?+

Local Zones (Hamburg, Helsinki, Warsaw, Edinburgh, etc.) extend AWS regions for ultra-low latency; Wavelength brings AWS to mobile carrier 5G networks. Most workloads don't need either. Use Local Zones if you have edge compute needs (gaming, AR/VR, real-time AI inference). Use Wavelength only if you're building 5G-native applications.

How do AWS Outposts fit into European architecture?+

AWS Outposts is for on-premises AWS hardware, typically used for data residency requirements that even AWS regions can't satisfy (e.g., truly air-gapped environments, defense applications). For most European founders, Outposts is overkill. AWS regions + appropriate compliance overlay covers regulatory needs.