eu-west-3: Europe (Paris)
eu-west-3 is the code for the Europe (Paris) region in France. It is enabled by default, sits inside the EU, and is chosen mainly by organisations that serve French users or whose customers and regulators expect data to be hosted in France.
Why choose Paris
Ireland and Frankfurt already cover France well for latency, so the case for Paris is usually about place rather than speed:
- French public bodies, health providers and large enterprises often ask suppliers for hosting in France specifically, not just "in the EU".
- Sector rules in France, such as those for health data, can require hosts with particular certifications. Check AWS's compliance programmes in AWS Artifact for the current scope rather than assuming eu-west-3 meets a given rule.
- For users in France, Belgium and Switzerland, Paris gives a short path for latency-sensitive workloads such as real-time bidding, gaming or voice.
If none of these apply, Ireland or Frankfurt may give you more services for a similar price, and Paris can still be added later for the customers who need it. Many teams run a single French deployment only for the contracts that demand it.
Configuring tools for eu-west-3
# one-off
aws cloudwatch describe-alarms --region eu-west-3 \
--state-value ALARM --query 'MetricAlarms[].AlarmName'
# per profile
aws configure set region eu-west-3 --profile fr
# per process
AWS_REGION=eu-west-3 ./deploy.shEndpoints follow <service>.eu-west-3.amazonaws.com, for instance ecs.eu-west-3.amazonaws.com. Note the easy slip between eu-west-3 (Paris) and eu-west-1 (Ireland); both are EU, but a contract that names France will not accept Ireland.
Service coverage
Paris has a broad catalogue, but it is not identical to Ireland's or Frankfurt's. Before you design around a specific managed service, GPU instance family or newer database engine, check the AWS Regional Services List and describe-instance-type-offerings for the region. A missing service discovered after a contract is signed tends to force either a different architecture or an awkward exception for data leaving France.
Neighbours and disaster recovery
| Region | Use it for |
|---|---|
| eu-central-1 (Frankfurt) | Common EU recovery partner with a large catalogue |
| eu-west-1 (Ireland) | Widest European service set |
| eu-south-2 (Spain) | Nearby EU region to the south; opt-in |
| eu-west-2 (London) | Close, but outside the EU |
There is only one AWS region in France, so if your residency rule is "France only", recovery has to happen across Availability Zones inside Paris, with backups protected in a separate account. If the rule is "EU", replicating to Frankfurt is straightforward.
Enforcing "France only"
Once you promise hosting in France, add a guardrail so it stays true: a service control policy that denies requests where aws:RequestedRegion isn't eu-west-3, with carefully chosen exceptions for global services such as IAM, Organizations and Support. Test it in a sandbox first; a blanket deny is the fastest way to lock yourself out of IAM changes during an incident.
Questions
Where is eu-west-3?
In the Paris area, France. It is the only AWS region in France.
Is eu-west-3 an opt-in region?
No, it is enabled by default in every account.
Which region should I use as DR for eu-west-3?
Frankfurt (eu-central-1) is the most common EU partner. If data must stay in France, use multiple Availability Zones in Paris instead.
Residency guardrails do their job quietly until someone hits an explicit deny during an incident. CloudConsole, a phone app for AWS, is built with production guardrails and per-region views of alarms and resources.
About the app → · Download on the App Store