Confluent Cloud Limits and Supported Features

Confluent Cloud has the following limits and supported features.

Features in Confluent Cloud

Description Confluent Cloud Enterprise Confluent Cloud
Auto topic creation No No
ACLs Yes Yes
Consumer lag UI

Yes

  • Disabled when VPC peered.
Yes
Cluster throughput
  • Write: Unlimited
  • Read: Unlimited
  • Write: Up to 100 MBps
  • Read: Up to 100 MBps
Data retention Unlimited 5 TB
Encryption at rest Yes (encrypted volumes) Yes (encrypted volumes)
Encryption in motion Yes (SSL/TLS) Yes (SSL/TLS)
Exactly Once Semantics Yes Yes
Key based compacted storage Yes Yes
Max clusters Unlimited 5
Max partitions Up to 100,000 2048
Max storage per partition 100 GB 100 GB
Max consumer groups Unlimited Unlimited
Max consumer group members Unlimited Unlimited
Max message size Default is 2 MB, but can be increased to 8 MB 2 MB
Multi-zone high availability Yes Yes
Network peering options
  • VPC peering
  • Transit Gateway on AWS
Not available
Role based access control Coming soon Coming soon
SAML integration Coming soon Coming soon
Service accounts Yes Yes
Schema Registry

Yes

  • Up to 1,000 schema versions are included. The quota can be increased up to 5,000 schema versions.
  • A single Schema Registry is available per environment (e.g. Prod, Dev)
  • For details, see Supported Features.

Yes

  • Up to 200 schema versions are included.
  • A single Schema Registry is available per environment (e.g. Prod, Dev)
  • For details, see Supported Features.
Support Yes Yes
Topic management UI Yes Yes
Uptime SLA Yes

Yes

  • For new clusters in some regions

Confluent Cloud Schema Registry

Schema Management is fully supported on Confluent Cloud with Schema Registry. Details are listed below.

Supported Features

  • A single Schema Registry is available per environment (e.g. Prod, Dev).
  • Access Control to Schema Registry is based on API key and secret.
  • Each environment must have at least one Apache Kafka® cluster to enable Schema Registry.
  • Your VPC must be able to communicate with the Confluent Cloud Schema Registry public internet endpoint. For more information, see Using Confluent Cloud Schema Registry in a VPC Peered Environment.
  • Available in the US, Europe, and APAC regions.

Learn More

Confluent Cloud Connect Preview

These Confluent Cloud connectors are available as a preview feature. A preview feature is a component of Confluent Platform that is being introduced to gain early feedback from developers. These features can be used for evaluation and non-production testing purposes or to provide feedback to Confluent. Comments, questions, and suggestions related to preview features are encouraged and can be submitted to ccloud-connect-preview@confluent.io.

Refer to Confluent Cloud connector limitations for details.

Confluent Cloud Data Flow Preview

Confluent Cloud Data Flow is currently available as a preview feature. A preview feature is a component of Confluent Platform that is being introduced to gain early feedback from developers. These features can be used for evaluation and non-production testing purposes or to provide feedback to Confluent. Comments, questions, and suggestions related to preview features are encouraged and can be submitted to ccloud-dataflow-preview@confluent.io.

For more information, see Data Flow.

Confluent Cloud KSQL Preview

Confluent Cloud KSQL is currently available as a preview feature. A preview feature is a component of Confluent Platform that is being introduced to gain early feedback from developers. These features can be used for evaluation and non-production testing purposes or to provide feedback to Confluent. Comments, questions, and suggestions related to preview features are encouraged and can be submitted to preview@confluent.io.

For more information, see the Create KSQL Streaming Queries in Confluent Cloud.

Supported Features

  • Web interface for managing your KSQL Cloud environment directly from your browser that exposes all critical KSQL information.
  • SQL editor to write, develop, and execute SQL queries with auto completion directly from the Web interface.
  • Integration with Confluent Cloud Schema Registry to leverage your existing schemas to use within your SQL queries.
  • Currently, user-defined functions aren’t supported in KSQL Cloud.
  • A maximum of 20 queries per application are allowed.
  • A maximum of 1 application is allowed.
  • Confluent Cloud KSQL Preview will be available in the following AWS regions: us-east-1, us-east-2, us-west-2, us-west-1, and eu-central-1.
  • Confluent Cloud KSQL Preview will be available in all GCP regions supported by Confluent Cloud.

Compliance

Description Confluent Cloud Enterprise Confluent Cloud
GDPR readiness Yes Yes
HIPAA Yes No
ISO 27001 Yes Yes
PCI level 2 Yes Yes
SOC 1, SOC 2, SOC 3 Yes Yes

Upgrade Policy

This section describes how changes to Confluent Cloud are managed for Major Upgrade, Deprecation, and Minor Upgrade.

Major Upgrade

Any change to Confluent Cloud services that requires code changes to any customer applications (Kafka clients, API integrations, etc) to continue working as before.

Potential customer impact
  • Large: could prevent use of service without code or configuration changes, or could problematically alter the performance profile.
  • None: totally transparent, depending on customer usage of the service.
Examples
  • Upgrading Kafka to a version that is not fully backwards-compatible with the previous version.
  • Updating a public API from api/v1/foo to api/v2/foo.
  • Security update that materially changes cluster or client throughput.
Frequency
Rare (~1 per year)
Communication before the change
  • Guaranteed: multiple email notifications to all registered Confluent Cloud users, starting at least 180 days before the upgrade date, with details about the change and available options.
  • May also include: in-app messaging; updated documentation and release notes; communication from Sales and customer support.
Timing of the change for each customer
May be coordinated with Confluent Cloud Enterprise customers to avoid high-risk times and make the upgrade sooner, but the final date set by Confluent is not negotiable.

Deprecation

Any removal of customer-usable functionality from Confluent Cloud services.

Potential customer impact
  • Large: could prevent use of service if the customer relies on the feature.
  • None: totally transparent, depending on customer usage of the service.
Examples
  • Complete removal of a feature from the UI.
  • Shutting down api/v1/foo.
  • Removing a particular Connector as an option.
Frequency
Rare (~1 per year)
Communication before the change
  • Guaranteed: multiple email notifications to all registered Confluent Cloud users, starting at least 180 days before the deprecation date, with details about the change and available alternatives.
  • May also include: in-app messaging; updated documentation and release notes; communication from Sales and customer support.
Timing of the change for each customer
100% at Confluent’s discretion.
Notes
Deprecations may be part of major upgrades (no guarantee of equivalent functionality in new versions).

Minor Upgrade

Any change to Confluent Cloud services that isn’t a major upgrade or deprecation.

Potential customer impact
  • Minimal: small negative effect for a short period.
  • None: totally transparent, depending on customer usage of the service.
Examples
  • Kafka cluster roll.
  • Upgrading Kafka to a fully backwards-compatible version.
  • Adding net new features.
Frequency
Very often, e.g., multiple times per day.
Communication before the change
None guaranteed, but may include email notifications, in-app messaging, updated documentation and release notes communication from Sales and customer operations.
Timing of the change for each customer
100% at Confluent’s discretion.

Cloud Providers & Regions

Tip

If you don’t see your region listed, contact Confluent. Additional regions can be supported by request.

  • Amazon Web Services (AWS)
    • ap-northeast-1 (Tokyo)
    • ap-south-1 (Mumbai)
    • ap-southeast-1 (Singapore)
    • ap-southeast-2 (Sydney)
    • ca-central-1 (Canada Central) [1]
    • eu-central-1 (Frankfurt)
    • eu-west-1 (Ireland)
    • eu-west-2 (London)
    • us-east-1 (N. Virginia)
    • us-east-2 (Ohio)
    • us-west-1 (N. California) [1]
    • us-west-2 (Oregon)
  • Azure (Microsoft Azure)
    • southeastasia (Singapore)
    • westus2 (Washington)
    • westeurope (Netherlands)
  • GCP (Google Cloud Platform)
    • asia-east2 (Hong Kong)
    • asia-northeast1 (Tokyo)
    • asia-southeast1 (Singapore)
    • australia-southeast1 (Sydney)
    • europe-north1 (Finland)
    • europe-west1 (Belgium)
    • europe-west2 (London)
    • europe-west3 (Frankfurt)
    • europe-west4 (Netherlands)
    • us-central1 (Iowa)
    • us-east1 (S. Carolina)
    • us-east4 (N. Virginia)
    • us-west1 (Oregon)
    • us-west2 (Los Angeles)
[1](1, 2) Region only supports single zone deployments of Confluent Cloud

Support

Description Confluent Cloud Enterprise Confluent Cloud
Support

Business (included):

  • 24 x 7 coverage
  • P1 issue response within 60 minutes

Premier (add-on):

  • 24 x 7 coverage
  • P1 issues response within 30 minutes
  • Assigned TAM, quarterly business and technical reviews

Basic

Developer

  • Business hours support
  • 24 x 7 access to support portal

Business

  • 24 x 7 coverage
  • 60 minutes response SLA

For more information, see How do I change support plans?