Yes — Amazon Connect is available in AWS GovCloud (US). It runs in the AWS GovCloud (US-West) Region, giving US government agencies and compliance-bound organisations a cloud contact centre inside AWS's isolated, government-focused environment. But it is not simply the commercial product in a different region — GovCloud comes with meaningful differences and a notable list of features that aren't available. [Source: AWS, Connect Customer in AWS GovCloud (US)]
What AWS GovCloud (US) Is
AWS GovCloud (US) consists of isolated AWS Regions designed to let US government agencies and customers move sensitive workloads to the cloud while meeting specific regulatory requirements — including FedRAMP High, DoD SRG Impact Levels 4 and 5, and CJIS. To help customers meet US export-control regimes such as ITAR and EAR, GovCloud Regions are administered exclusively by AWS personnel who are US citizens, and are appropriate for Controlled Unclassified Information (CUI) and unclassified data. [Source: AWS, What Is AWS GovCloud (US)?]
In short: GovCloud exists so agencies and regulated organisations can run exactly these kinds of workloads — a contact centre handling citizen or sensitive data — within an environment built around US federal compliance and export-control obligations.
How Amazon Connect in GovCloud Differs
Several specific differences apply to Amazon Connect in GovCloud compared with the commercial Regions:
- Dedicated domain. Instances use the
*.govcloud.connect.awsdomain. - Latest CCP only. It supports only the latest Contact Control Panel for voice and chat; the earlier CCP isn't available.
- Latest contact search only. Only the newest contact search experience is supported.
- Separate partition. This is the big architectural one — see below.
[Source: AWS, Connect Customer in AWS GovCloud (US)]
The Separate Partition: No Cross-Partition Integration
Amazon Connect in AWS GovCloud (US) sits in a separate partition from all commercial Regions. That means it does not support cross-partition integration with commercial-Region AWS services — including Amazon Lex, AWS Lambda, Amazon Kinesis, Amazon S3, and Amazon CloudWatch, among others. [Source: AWS, Connect Customer in AWS GovCloud (US)]
Why this matters a lot: on commercial Amazon Connect, almost every non-trivial flow calls Lambda for data dips, uses Lex for self-service, and streams to Kinesis/S3 for analytics. In GovCloud you can only integrate with services available within the GovCloud partition — so your architecture for flows, integrations, and analytics has to be designed around that from the start, not retrofitted.
Features Not Available in GovCloud
This is the list to check before committing. The following Amazon Connect features are not currently available in AWS GovCloud (US): [Source: AWS, Connect Customer in AWS GovCloud (US)]
| Not available in GovCloud | What that means for you |
|---|---|
| Agentic CX Designer (ACXD) | No agentic AI self-service application layer |
| AI agents | No native agentic AI agents |
| Email channel | Voice and chat only, not email |
| Cases | No native case management |
| Outbound campaigns | No outbound campaign capability |
| Customer Profiles | No unified customer profile feature |
| Conversational analytics AI features | The AI-driven analytics (formerly Contact Lens) aren't available |
| Live media streaming | Not supported |
| Apple Business Chat integration | Not supported for chat |
The headline for 2026: if your use case depends on the newer AI capabilities — ACXD, AI agents, or AI conversational analytics — those are not in GovCloud today. For many agencies the core omnichannel contact centre (voice, chat, skills-based routing, real-time and historical analytics) is exactly what's needed; just confirm the specific features you're counting on are available before you plan around them.
Also Worth Knowing
- Phone numbers: GovCloud (US-West) is specifically excluded from the standard list of Regions where you can order and port phone numbers, so number provisioning needs checking for your deployment. [Source: AWS, Region requirements for ordering and porting phone numbers]
- Export-controlled content: AWS states that Amazon Connect instance and resource configuration metadata (names, aliases, descriptions, tags on instances, users, queues, routing profiles, contact flows, report names) is not permitted to contain export-controlled data. [Source: AWS, Connect Customer in AWS GovCloud (US)]
Always verify current status. Feature availability and compliance authorisations in GovCloud change over time as AWS brings more capabilities into the partition. Treat the list above as current-at-time-of-writing and confirm the specifics for your use case in the official AWS GovCloud and Amazon Connect documentation before making decisions.
Frequently Asked Questions
Is Amazon Connect available in AWS GovCloud?
Yes. Amazon Connect (Amazon Connect Customer) is available in the AWS GovCloud (US-West) Region. GovCloud consists of isolated AWS Regions designed for US government agencies and customers with regulatory requirements including FedRAMP High, DoD SRG Impact Levels 4 and 5, and CJIS, and it is administered exclusively by AWS personnel who are US citizens to support ITAR and EAR obligations.
What compliance does Amazon Connect in GovCloud support?
AWS GovCloud (US) addresses FedRAMP High, DoD SRG Impact Levels 4 and 5, and CJIS requirements, and is appropriate for Controlled Unclassified Information (CUI) and unclassified data. GovCloud Regions are administered only by US citizens to help customers meet ITAR and EAR export-control obligations. Always confirm the current authorisation status for your specific use case in AWS's documentation.
Which Amazon Connect features are not available in GovCloud?
In AWS GovCloud (US), Amazon Connect does not currently offer Agentic CX Designer (ACXD), AI agents, the email channel, Cases, outbound campaigns, Customer Profiles, conversational analytics AI features, live media streaming, and Apple Business Chat integration. It also runs in a separate partition, so it does not support cross-partition integration with commercial-region services like Lex, Lambda, Kinesis, S3, and CloudWatch.
Can Amazon Connect in GovCloud integrate with Lambda and Lex?
Not across partitions. Amazon Connect in AWS GovCloud (US) is in a separate partition from all commercial Regions, so it cannot integrate with commercial-Region instances of Lex, Lambda, Kinesis, S3, CloudWatch, and similar services. Any integrations must use services available within the GovCloud partition, which changes how you architect flows, data dips, and analytics.
Conclusion
Amazon Connect is available in AWS GovCloud (US-West), bringing the core omnichannel contact centre into AWS's FedRAMP High / DoD IL-4 and IL-5 / CJIS / ITAR-aligned environment — a strong fit for government agencies and regulated organisations handling sensitive or Controlled Unclassified Information. The trade-off is the separate partition (no cross-partition integration with commercial services like Lex, Lambda, and S3) and a specific list of features that aren't available, most notably the newer AI capabilities such as ACXD, AI agents, Customer Profiles, Cases, and AI conversational analytics. Confirm the exact features and compliance authorisations you need against current AWS documentation before you design around GovCloud.