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 No
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 100000 2048
Max consumer groups Unlimited Unlimited
Max consumer group members Unlimited Unlimited
Max message size Default is 2 MB, but can be increased to 6 MB 2 MB
Multi-zone high availability Yes No
Role based access/ACLs Coming soon No
SAML integration Coming soon No
Service accounts Yes No
Schema Registry

Yes (Preview)

  • 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 (Preview)

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

Yes

  • Disabled when VPC peered.
Yes
VPC peering

Yes

  • Topic management, consumer lag, and KSQL are disabled in the UI when VPC peered.
No

Confluent Cloud Schema Registry Preview

Confluent Cloud Schema Registry is 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-sr-preview@confluent.io.

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.
  • Only available in the US region.

For more information, see Confluent Cloud Quick Start.

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 the following for specific preview connector limitations.

Confluent Cloud S3 Connector (Sink)

The following are specific limitations for the Confluent Cloud S3 Connector (Sink).

  • The Confluent Cloud cluster and the target S3 bucket must be in the same AWS region.
  • flush.size is set at 1000.
  • schema.compatibility is set to NONE.
  • Partitioning (hourly or daily) is based on Kafka record time.
  • A valid schema must be available in Confluent Cloud Schema Registry to use Avro.
  • For Confluent Cloud, organizations are limited to one connector. Use of this connector is free for a limited time.
  • For Confluent Cloud Enterprise, organizations are limited to 20 tasks. Additionally, please contact your Confluent account manager to participate in the Confluent Cloud S3 Connector (Sink) preview.

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 Confluent Cloud KSQL Quick Start.

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 No
PCI level 2 Yes No
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.

Description Confluent Cloud Enterprise Confluent Cloud
Amazon Web Services (AWS)

Supported in these regions:

  • ap-southeast-1 (Singapore)
  • ap-southeast-2 (Sydney)
  • ca-central-1 (Canada Central)
  • eu-west-1 (Ireland)
  • eu-central-1 (Frankfurt)
  • us-east-1 (N. Virginia)
  • us-east-2 (Ohio)
  • us-west-1 (N. California)
  • us-west-2 (Oregon)

Supported in these regions:

  • ap-southeast-1 (Singapore)
  • ap-southeast-2 (Sydney)
  • ca-central-1 (Canada Central)
  • eu-west-1 (Ireland)
  • eu-central-1 (Frankfurt)
  • us-east-1 (N. Virginia)
  • us-east-2 (Ohio)
  • us-west-1 (N. California)
  • us-west-2 (Oregon)
AWS multi-zone high availability

Supported in these regions:

  • us-east-1
  • us-east-2
  • us-west-1
  • us-west-2
  • eu-west-1
  • eu-central-2
  • ap-southeast-1
  • ap-southeast-2
Not supported
GCP (Google Cloud Platform)

Supported in these regions:

  • asia-east2 (Hong Kong)
  • australia-southeast1 (Sydney)
  • europe-north (Finland)
  • europe-west1 (Belgium)
  • europe-west2 (London)
  • europe-west3 (Frankfurt)
  • us-central1 (Iowa)
  • us-east4 (N. Virginia)
  • us-west2 (Los Angeles)

Supported in these regions:

  • asia-east2 (Hong Kong)
  • australia-southeast1 (Sydney)
  • europe-north (Finland)
  • europe-west1 (Belgium)
  • europe-west2 (London)
  • europe-west3 (Frankfurt)
  • us-central1 (Iowa)
  • us-east4 (N. Virginia)
  • us-west2 (Los Angeles)
GCP multi-zone high availability

Supported in these regions:

  • us-central1
  • us-east4
  • europe-west1
  • europe-west2
Not supported
Microsoft Azure Contact Confluent Contact Confluent

Support

Description Confluent Cloud Enterprise Confluent Cloud
Support
  • Gold support
  • 24x7 access
  • 1-hour response time for critical problems
Community