eu-west-1 is Ireland, eu-west-2 is London, eu-west-3 is Paris, eu-central-1 is Frankfurt, eu-north-1 is Stockholm, eu-south-1 is Milan, eu-south-2 is Spain and eu-central-2 is Zurich. This guide compares them on service availability, latency from UK and EU cities and compliance posture, so a European team can pick one in an afternoon.
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 launch.
Region selection is the foundation. Get it wrong and everything compounds.
| Code | Name | City | Availability Zones | Opt-in | Opened |
|---|---|---|---|---|---|
| eu-west-1 | Europe (Ireland) | Dublin | 3 | Not required | 2008 |
| eu-central-1 | Europe (Frankfurt) | Frankfurt | 3 | Not required | 2014 |
| eu-west-2 | Europe (London) | London | 3 | Not required | 2016 |
| eu-west-3 | Europe (Paris) | Paris | 3 | Not required | 2017 |
| eu-north-1 | Europe (Stockholm) | Stockholm | 3 | Not required | 2018 |
| eu-south-1 | Europe (Milan) | Milan | 3 | Required | 2020 |
| eu-south-2 | Europe (Spain) | Aragon | 3 | Required | 2022 |
| eu-central-2 | Europe (Zurich) | Zurich | 3 | Required | 2022 |
Source: AWS Regions documentation, read 7 November 2026. Opt-in means the region is disabled by default on accounts and must be enabled first. Opened years are from each region's AWS launch announcement.
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.
Every region has different service availability, attestation coverage, and cost profile. Below is the practitioner-grade detail.
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)
Single-region is enough for most workloads. Multi-region adds operational complexity. Three patterns cover ~95% of real-world EU multi-region needs.
Announced in 2023 and open since January 2026, with its first region in Brandenburg, Germany, 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.
Tell us where your users are, what data you hold and which rules apply to you. We reply within one business day with a region recommendation and the reasoning behind it.
Have a specific scenario? Book a 30-min call and we'll work through your exact decision factors.
Book Free Region Review →Whether you're starting fresh, evaluating multi-region, or considering AWS European Sovereign Cloud, share your workload context and we'll recommend the specific region (or region pair) that fits.
★ AWS Advanced Tier Services Partner · ISO 27001:2022 · ISO 9001:2015 · 5× AWS-Certified Founder