Confluent Cloud for Government¶
Confluent Cloud for Government is FedRAMP Ready
FedRAMP Ready status marks an essential milestone in providing secure data streaming services to government agencies. This status, as attested by a Third Party Assessment Organization (3PAO) and deemed acceptable by the FedRAMP PMO, signifies Confluent’s commitment to rigorous security standards, making it a significant step toward full FedRAMP authorization.
You must contact Confluent to setup a Confluent Cloud for Government organization before you can use the service.
Confluent Cloud for Government is an Early Access release.
Confluent uses Early Access releases to gather feedback. Early Access is intended for evaluation use in development and non-production testing environments or to provide feedback to Confluent, particularly as it becomes more widely available in follow-on preview editions. The warranty, SLA, and Support Services provisions of your agreement with Confluent do not apply to Early Access. Confluent considers Early Access to be a Proof of Concept as defined in the Confluent Cloud Terms of Service. Confluent may discontinue providing preview releases of the Early Access releases at any time at the sole discretion of Confluent.
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.
What is Confluent Cloud for Government?¶
Confluent Cloud for Government is a fully-managed event streaming service for the U.S. government, developed by the same people that built Confluent Cloud. 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 Support and Billing.
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 |
| [*] | Not all cluster types are supported. See API availability comparison table. |
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 supported in a fully-managed fashion in Confluent Cloud for Government. You can self-host these features. For more information, see Confluent Cloud for Government and Self-managed Components.
- Kafka Connect
- Confluent Cloud Schema Registry
- Flink jobs
- Confluent Replicator
- Confluent Cluster Linking
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:
- Northwestern US (us-gov-west-1)
- Eastern US (us-gov-east-1)