eu-central-1: Europe (Frankfurt)
eu-central-1 is the code for the Europe (Frankfurt) region in Germany. It is enabled by default, sits inside the EU, and is the usual choice for German and central European customers, for workloads that must keep data in Germany, and as the EU recovery partner for Ireland.
Why Frankfurt
Frankfurt is one of Europe's biggest internet interconnection hubs, which makes it a good network position for users across Germany, Austria, Switzerland, Poland and the rest of central and eastern Europe. Three reasons dominate when teams choose it:
- German data location. Many German enterprises, Mittelstand suppliers and public bodies ask for data to be stored in Germany, not just the EU. Frankfurt is AWS's long-standing answer.
- Latency to the DACH region and further east. For interactive applications serving these markets, it usually beats Ireland.
- A large, mature region. It has a wide service catalogue and plenty of capacity, so it works as a primary region in its own right, not only as a residency option.
Frankfurt vs Ireland
| eu-central-1 (Frankfurt) | eu-west-1 (Ireland) | |
|---|---|---|
| Country | Germany | Ireland |
| Best-served users | Central and eastern Europe | UK, Ireland, western Europe, transatlantic |
| New services | Usually early, sometimes after Ireland | Often first in Europe |
| Price | Often slightly higher for compute | Often slightly lower |
Treat the price row as a prompt to check, not a rule: run your main line items through the Pricing Calculator for both. Many organisations end up using both regions, one as primary and the other for recovery.
Targeting eu-central-1
aws ecs list-clusters --region eu-central-1
export AWS_REGION=eu-central-1
# check where an existing bucket lives
aws s3api get-bucket-location --bucket my-bucketEndpoints follow <service>.eu-central-1.amazonaws.com, for example s3.eu-central-1.amazonaws.com. Frankfurt only accepts Signature Version 4 for S3, which has been the SDK default for years; you only meet this with very old tools or hand-rolled signing code, where it shows up as an authorisation error naming the signing mechanism.
Residency: what Frankfurt does and doesn't settle
Running in eu-central-1 puts your resources in Germany. It doesn't, on its own, control who can access them, where support engineers sit, or where data goes once your own application sends it to an analytics or logging tool. If a customer requires stronger sovereignty assurances, review AWS's published data-protection commitments and consider the separate AWS European Sovereign Cloud that AWS has announced; it is a distinct offering, not a setting on eu-central-1.
Whatever the requirement, enforce it in code: an SCP that denies aws:RequestedRegion outside your approved list keeps a stray deployment from landing in us-east-1.
Neighbouring regions
eu-central-2 (Zurich) serves Swiss requirements and is opt-in. eu-west-1, eu-west-3 and eu-north-1 are the EU options for recovery. eu-south-1 in Milan sits to the south. Check service coverage in the recovery region before you depend on it.
A practical tip if you run in both Frankfurt and Ireland: tag or name resources with the region code, and set different console colours or account aliases for each. Engineers flipping between the two during an incident make mistakes when the screens look identical.
Questions
Where is eu-central-1?
In Frankfurt am Main, Germany.
Is eu-central-1 cheaper than eu-west-1?
Usually not; Ireland is often slightly cheaper for compute. Compare the specific services you use, as differences vary.
Is eu-central-1 GDPR compliant?
A region can't be compliant on its own. eu-central-1 keeps your data in Germany, inside the EU, which helps, but GDPR compliance depends on how you process and protect that data.
If your stack lives in Frankfurt, its alarms will fire on Central European Time whether or not you're at a desk. CloudConsole, a phone app for AWS, is built to show alarms, logs and resources on your phone.
About the app → · Download on the App Store