eu-west-1: Europe (Ireland)
eu-west-1 is the code for the Europe (Ireland) region, located in the Dublin area. It is AWS's oldest European region, enabled by default, inside the EU, and usually the European region with the broadest set of services, which is why many companies treat it as their default for Europe.
Where eu-west-1 is and why it's the default for Europe
The region sits in and around Dublin. Ireland's position on the transatlantic cable routes gives it good connectivity to both the UK and North America, and its place in the EU means data stored here is inside the European Union for GDPR purposes.
Because it was AWS's first region in Europe, it accumulated the most services and the most customers. In practice that means new services and instance types tend to reach Ireland before other European regions, and many SaaS vendors' "EU" hosting option is eu-west-1 under the hood.
The flip side of popularity is scale of impact: when Ireland has a regional event, a long list of European services and third-party tools degrade at the same time, which can make it harder to tell whose problem you are looking at. Keep a second source of truth for your own health, such as alarms in another region or synthetic checks from outside AWS.
When to pick Ireland, and when not to
| Situation | Better choice |
|---|---|
| EU customers, no country-specific rule, want the widest services | eu-west-1 |
| Data must stay in Germany, or users are mostly in central/eastern Europe | eu-central-1 (Frankfurt) |
| UK public sector or a contract requiring UK hosting | eu-west-2 (London) |
| French customers asking for hosting in France | eu-west-3 (Paris) |
| Cost-sensitive compute with flexible location | Compare with eu-north-1 (Stockholm) |
Price differences between European regions are real but vary by service; Ireland is often a little cheaper than Frankfurt for EC2, but check the specific items in the Pricing Calculator rather than assuming.
Using eu-west-1 in the CLI, SDKs and config
aws sqs list-queues --region eu-west-1
# ~/.aws/config
[profile eu]
region = eu-west-1
output = json
# environment
export AWS_REGION=eu-west-1Endpoints follow <service>.eu-west-1.amazonaws.com, for example logs.eu-west-1.amazonaws.com. For S3 buckets created via the API, pass LocationConstraint=eu-west-1; the legacy value EU also maps to Ireland but is best avoided in new code because it confuses readers.
Disaster recovery inside the EU
If your data has to stay in the EU, pair Ireland with Frankfurt, Paris, Stockholm, Milan or Spain rather than London, which is outside the EU after Brexit. Frankfurt is the most common pair because of its size and service coverage. For the recovery region, copy backups across accounts as well as regions so a compromised production account can't delete both.
Things people get wrong with eu-west-1
- Confusing it with eu-west-2. The codes differ by one digit but are different countries; a misconfigured pipeline can quietly move data from the EU to the UK.
- Assuming Ireland means GDPR compliance. Location is one part; access controls, processor agreements and transfers to support tools matter as much.
- Forgetting the global anchors. CloudFront certificates and billing alarms still belong in us-east-1, even for a fully European stack.
Questions
What is eu-west-1?
The AWS region code for Europe (Ireland), AWS's oldest region in Europe, located in the Dublin area.
Where is eu-west-1 located?
In Ireland, around Dublin. AWS doesn't publish individual data-centre addresses.
Is eu-west-1 in the EU?
Yes. Ireland is an EU member state, so data stored in eu-west-1 stays in the European Union.
Most European on-call engineers end up debugging something in Ireland eventually, often off-hours. CloudConsole, a phone app for AWS, is built to show that region's alarms and logs on your phone.
About the app → · Download on the App Store