Confluent Cloud for Government

This documentation provides broad comparisons between Confluent Cloud for Government and commercial Confluent Cloud. Many procedures and references for the two services are identical. Consider using this approach with this documentation:

Use this documentation to discover unique information about Confluent Cloud for Government
Use Confluent Cloud documentation to manage Confluent Cloud for Government

This guide assumes your familiarity with Confluent Cloud.

Confluent Cloud for Government is FedRAMP 20x Moderate authorized

Confluent Cloud for Government is authorized at the FedRAMP 20x Moderate impact level, providing U.S. public sector agencies and their partners with a fully managed data streaming platform that meets stringent federal security requirements for protecting mission‑critical workloads.

Marketplace listing: Confluent Cloud for Government (CCG) | FedRAMP Marketplace
Next Ongoing Authorization Report (OAR) date: June 16, 2026
Authority to Operate (ATO) letter: Confluent Trust Center US Public Sector Documents section

To use this service, email Confluent FedRAMP at FedRAMP@confluent.io to set up a Confluent Cloud for Government organization. For full authorization details, see FedRAMP Authorization Information for Confluent Cloud for Government.

What is Confluent Cloud for Government?

Confluent Cloud for Government is a fully managed, cloud-native Kafka service for connecting and processing data in a cloud computing environment, developed by the same people that built Confluent Cloud. You can focus on business needs instead of managing the underlying infrastructure that supports your Kafka instances. Confluent Cloud for Government is available to federal, state, local, and tribal governments; research institutions; and government contractors.

Confluent Cloud for Government comprises two components: the Cloud Control Plane and the Data Plane (Kafka clusters). The Cloud Control Plane runs in AWS GovCloud and Google Cloud. You use the Control Plane to select and deploy managed Kafka resources to a satellite cluster.

A satellite cluster consists of one or more Kubernetes nodes running Kafka, with one or more availability zones deployed based on customer-selected options. You can deploy a satellite cluster to AWS GovCloud. The Control Plane manages resources in satellite clusters using the Control Pipeline. All customer data remains in satellite clusters, isolated from the Control Plane.

This topic provides an overview of the supported Confluent Cloud for Government features and the available cloud providers and regions. For information about billing and support, see Billing and Support. For FedRAMP authorization information, see FedRAMP Authorization Information for Confluent Cloud for Government.

Supported features for Confluent Cloud for Government

Confluent Cloud for Government supports a subset of Confluent Cloud features.

API availability comparison table

The following table identifies the APIs supported for Confluent Cloud for Government.

Feature	API	Commercial supports	Confluent Cloud for Government supports
Billing	Costs-(billingv1)	Latest version	Latest version
Bring Your Own Key (BYOK)	Keys-(byokv1)	Latest version	Latest version
Cluster management	Clusters-(cmkv2)	Latest version	Latest version [*]
Identity and Access Management (IAM)	API-Keys-(iamv2)	Latest version	Latest version
	Users-(iamv2)	Latest version	Latest version
	Service-Accounts-(iamv2)	Latest version	Latest version
	Invitations-(iamv2)	Latest version	Latest version
	Role-Bindings-(iamv2)	Latest version	Latest version
	Identity-Providers-(iamv2)	Latest version	Latest version
	Jwks-(iamv2)	Latest version	Latest version
	Identity-Pools-(iamv2)	Latest version	Latest version
Kafka API	Cluster-(v3)	Latest version	Latest version
	Configs-(v3)	Latest version	Latest version
	ACL-(v3)	Latest version	Latest version
	Consumer-Group-(v3)	Latest version	Latest version
	Partition-(v3)	Latest version	Latest version
	Topic-(v3)	Latest version	Latest version
	Records-(v3)	Latest version	Latest version
	Cluster-Linking-(v3)	Latest version	Latest version
Metrics	Version-2	Latest version	Latest version
Networking	Networks-(networkingv1)	Latest version	Latest version
	Peerings-(networkingv1)	Latest version	Latest version
	Transit-Gateway-Attachments-(networkingv1)	Latest version	No support
	Private-Link-Accesses-(networkingv1)	Latest version	Latest version
	Network-Link-Services-(networkingv1)	Latest version	Latest version
	Network-Link-Endpoints-(networkingv1)	Latest version	Latest version
	Network-Link-Service-Associations-(networkingv1)	Latest version	Latest version
Notifications	Subscriptions-(notificationsv1)	Latest version	Latest version
	Integrations-(notificationsv1)	Latest version	Latest version
	Notification-Types-(notificationsv1)	Latest version	Latest version
Organizations	Organizations-(orgv2)	Latest version	Latest version
	Environments-(orgv2)	Latest version	Latest version

Kafka cluster types

Confluent Cloud for Government supports Dedicated Kafka cluster types.

No support for any other Kafka cluster types. For more information on Kafka cluster types, see Confluent Cloud Cluster Types in the commercial Confluent Cloud documentation.

Self-hosted options

Some Confluent Cloud features are not fully managed in Confluent Cloud for Government:

Kafka Connect
Confluent Cloud Schema Registry
Flink jobs
Confluent Replicator
Confluent Cluster Linking

You can self-host these features. For more information, see Confluent Cloud for Government and Self-Managed Components.

Supported cloud providers and regions for Confluent Cloud for Government

When you create a Kafka cluster in Confluent Cloud for Government, you must designate a government (gov) region. You cannot deploy clusters across government and standard regions. AWS is the only cloud provider for Confluent Cloud for Government.

AWS GovCloud

AWS GovCloud regions meet stringent U.S. government security requirements. To learn more, see the AWS GovCloud documentation.

You can deploy Kafka clusters in the following government regions:

AWS GovCloud US-West: us-gov-west-1
AWS GovCloud US-East: us-gov-east-1