Which AWS region should I choose for Amazon Connect?
You choose the region when you create an Amazon Connect instance, and you can't move the instance later. The region decides which features you get, which countries outbound campaigns can call, where contact data is stored, and which region your disaster-recovery copy can use. Use the region finder above to tick the features you need and see which regions support all of them.
1. Start with data residency and your customers
- Data residency: recordings, transcripts and contact records are stored in the instance's region. If your customers' data must stay in a country or the EU, that usually decides the region before anything else.
- Outbound campaigns: each region can call only certain countries. For example, the US regions call the US, Mexico and Brazil; Frankfurt and London call 11 European countries including the UK; Singapore calls Singapore, Thailand, Malaysia, the Philippines and Vietnam. Pick a customer country in the finder to check.
- Phone numbers and latency: agents and callers far from the region get more audio delay. Pick the region closest to most of your callers and agents.
2. Check the features you need
Nine regions — N. Virginia, Oregon, Canada, Frankfurt, London, Singapore, Sydney, Tokyo and Seoul — support almost everything, including agentic voice, agent assist and the generative AI analytics. The main gaps are:
- Africa (Cape Town): no agentic voice, agent assist, Voice ID, live media streaming, Apple Messages, push notifications or forecasting and scheduling. External voice analytics is recording only.
- AWS GovCloud (US-West): for US government workloads. The core contact centre, Contact Lens analytics, tasks, the data lake and forecasting are available. Most digital channels, Customer Profiles, Cases and AI agents are not, and outbound campaigns are API only.
- Voice ID is also not available in Seoul. Generative AI categorisation is not listed for Singapore, and generative AI evaluations are not listed for Seoul.
3. Plan disaster recovery
Global Resiliency works only in three region pairs: N. Virginia with Oregon, Frankfurt with London, and Tokyo with Osaka. Either region in a pair can be the primary. AWS enables it on request through your account team. If you might need it later, choosing a region in one of these pairs keeps that option open. The replica needs the same service quotas as the primary, which the Service Quota Planner can work out.
4. Before you commit
- Compare two candidate regions with Compare two regions. It shows only what differs.
- Check costs with the pricing calculator. Telephony rates depend on the country.
- Get the firewall allowlist for the region from the Allowlist Auditor.
- AWS adds features to regions often, so confirm on the AWS page before you sign off. The date this matrix was last checked is shown at the top.