FAQ for Confluent Cloud¶
This topic provides answers to general Confluent Cloud questions.
- How does pricing and billing work for Confluent Cloud?
- What cloud providers are supported?
- What compliance standards does Confluent Cloud offer?
- What version of Kafka does Confluent Cloud use?
- What client and protocol versions are supported?
- How do I sign up for Confluent Cloud?
- How do I connect to Confluent Cloud?
- How do I grant other users access to my cluster?
- Can I be auto-notified about failures or incidents?
- Can I do unlimited retention using log compacted topics with Confluent Cloud?
- Are there topic or partition limits?
- How do I change support plans?
- What specific security features does Confluent Cloud offer?
- What version of TLS is supported on Confluent Cloud?
- Is Kerberos supported on Confluent Cloud?
- Are Confluent Cloud IP addresses static?
- What are the recommended JVM settings?
- Can I switch between Confluent Cloud cluster types?
- Can I use the same email account for multiple Confluent Cloud organizations?
- Why do I see the same bootstrap server for different clusters?
- Can I access broker logs?
If you don’t see your region listed, contact Confluent. Additional regions can be supported by request.
- Amazon Web Services (AWS)
- af-south-1 (Cape Town)
- ap-east-1 (AWS Hong Kong)
- ap-northeast-1 (Tokyo)
- ap-northeast-2 (Seoul)
- ap-south-1 (Mumbai)
- ap-southeast-1 (Singapore)
- ap-southeast-2 (Sydney)
- ca-central-1 (Canada Central)
- eu-central-1 (Frankfurt)
- eu-north-1 (Stockholm)
- eu-south-1 (Milan)
- eu-west-1 (Ireland)
- eu-west-2 (London)
- eu-west-3 (Paris)
- me-south-1 (Bahrain)
- sa-east-1 (São Paulo)
- us-east-1 (N. Virginia)
- us-east-2 (Ohio)
- us-west-1 (N. California) (Only supports Single-Zone (SZ) dedicated clusters with PrivateLink/VPC peering/Transit Gateway.)
- us-west-2 (Oregon)
- Azure (Microsoft Azure)
- australiaeast (New South Wales)
- brazilsouth (Brazil South)
- canadacentral (Canada)
- centralus (Iowa)
- eastus (Virginia)
- eastus2 (Virginia)
- francecentral (France)
- germanywestcentral (Germany West Central)
- japaneast (Japan East)
- northeurope (Ireland)
- southafricanorth (South Africa North)
- southcentralus (South Central US)
- southeastasia (Singapore)
- uksouth (London)
- westeurope (Netherlands)
- westus2 (Washington)
- GCP (Google Cloud Platform)
- asia-east1 (Taiwan)
- asia-east2 (Hong Kong)
- asia-northeast1 (Tokyo)
- asia-northeast3 (Seoul)
- asia-south1 (Mumbai)
- asia-southeast1 (Singapore)
- asia-southeast2 (Jakarta)
- australia-southeast1 (Sydney)
- europe-central2 (Warsaw)
- europe-north1 (Finland)
- europe-west1 (Belgium)
- europe-west2 (London)
- europe-west3 (Frankfurt)
- europe-west4 (Netherlands)
- europe-west6 (Zurich)
- northamerica-northeast1 (Montreal)
- southamerica-east1 (São Paulo)
- us-central1 (Iowa)
- us-east1 (S. Carolina)
- us-east4 (N. Virginia)
- us-west1 (Oregon)
- us-west2 (Los Angeles)
- us-west4 (Las Vegas)
For information on compliance and security, see https://www.confluent.io/trust-and-compliance/.
Confluent Cloud runs the latest version of Confluent Platform, including all released and to-be-released updates.
- After a new version of Kafka is released, there is an expected lag before all Confluent Cloud clusters are updated with the latest.
- Not all current Confluent Platform features are available in Confluent Cloud.
Since Kafka version 0.10.0.0, clients and brokers provide backward compatibility so that they can fall back to older request types or throw appropriate errors if functionality is not available. This means that upgrades to Kafka clients do not require corresponding broker upgrades and upgrades to the Kafka version running in Confluent Cloud do not require corresponding version upgrades on the client side. However, it is strongly recommended that you keep all of your clients running on the latest version so that you get the best performance and can use the latest features. For more information, see Confluent Platform and Apache Kafka Compatibility.
- Confluent Cloud follows the Confluent Platform client version support policy.
- Compatible clients must support and implement TLS/SSL encryption and SASL_PLAIN authentication. This is required to connect to Confluent Cloud.
- All client features since 0.10.0.0 are supported, including exactly-once delivery semantics.
Yes, you can view and subscribe to the Confluent Cloud status page.
Yes. You can set retention per topic in Confluent Cloud, including unlimited retention with log compaction. You are only limited by the amount of total storage for your cluster.
Yes, these are described in Confluent Cloud Features and Limits by Cluster Type. If you try to create more partitions than you are allowed, you will see this error:
"You may not create more than the maximum number of partitions"
You can manage your support plan by clicking the lifesaver icon in the upper-right corner of the Confluent Cloud window. From the menu that appears, click Support Plans.
The Support Plans page shows which plan you have currently. You can also choose a different plan from this page by clicking Select in the description of the plan. The next window that opens shows the pricing details for that plan and asks you to confirm your support plan upgrade. Click Confirm upgrade to upgrade, or click Close to cancel.
Downgrade restrictions apply to support plan purchases. Your current support level will stay in effect until the end of the current calendar month. However, if you downgrade within the month of purchase, your current support plan level is maintained until the end of the next full calendar month.
- All traffic over the wire requires TLS/SSL encryption and SASL_PLAIN authentication.
- All data is encrypted at rest on encrypted volumes. Confluent Cloud ensures encryption on customer data stored at rest through the native encryption services offered by our cloud providers.
- BYOK encryption is supported for data at rest on AWS dedicated clusters.
- You control the API keys and secrets specific to your cluster which you can revoke or reissue if necessary.
- All data is stored on secure infrastructure, with access controls that are restricted to Confluent engineers, inside a Confluent controlled VPC.
- Confluent Cloud Dedicated clusters provide dedicated compute and storage resources.
- VPC Peering (optional) provides network-level security for customers with Dedicated Clusters in Confluent Cloud.
- Single sign-on (SSO) using your existing SAML-based identity provider (IdP). Confluent Cloud SSO provides access control for multiple independent software systems.
TLS version 1.2 is supported.
Effective March 15, 2020, connections made by using TLS 1.0 and 1.1 are no longer supported. TLS 1.0 and 1.1 are legacy cryptographic protocols that do not support modern cryptographic algorithms. They contain security vulnerabilities that can be exploited by attackers. The Internet Engineering Task Force is planning to officially deprecate both protocols. The majority of encrypted internet traffic is now over TLS 1.2. TLS 1.2 has been the recommended version for IETF protocols since 2008.
No. Because the cloud infrastructure that is used by Confluent Cloud does not guarantee static IPs across cluster changes, DNS is used to provide a consistent address. The underlying IPs may be stable for some period of time, but are subject to change at any time, so they should not be relied upon for any use.
However, DNS for each cluster follows a predictable pattern. If your cluster bootstrap URL is
pkc-12345.<region>.<cloud>.<tld>, all broker endpoints will be of the format:
b0-pkc-12345.<region>.<cloud>.<tld>, b1-pkc-12345.<region>.<cloud>.<tld>, b2-pkc-12345.<region>.<cloud>.<tld>...
Here are the recommended JVM producer settings.
- JVM Security configuration
java.security.Security.setProperty(“networkaddress.cache.ttl” , “30"); java.security.Security.setProperty(“networkaddress.cache.negative.ttl” , “0");
- Kafka Producer and Consumer configuration
You can upgrade Basic clusters to Standard clusters. No other changes to cluster type (including downgrading a Standard cluster to Basic) are supported. For more information on cluster types, see Confluent Cloud Features and Limits by Cluster Type.
No, an email account can only be in one organization at a time. If you are changing
organizations, Confluent support can move your user account to a different organization.
If your email provider supports tagging with a plus sign (
+), then you can register
a new account using your existing email address with a different tag.
For example, if you have an existing Confluent Cloud user account using
email@example.com then you could register a
separate user account with this syntax:
In the Confluent Cloud web UI, you may see the same bootstrap server for different clusters. This is working as designed; it occurs because Confluent Cloud clusters are multi-tenant.
Kafka broker logs are not available in Confluent Cloud, but there are several tools to help you debug your streaming applications. The Confluent Cloud Metrics API provides actionable operational metrics about your Confluent Cloud deployment. The web UI shows cluster activity and usage relative to your cluster’s capacity. The UI also includes topic management and consumer lag monitoring. Developing Client Applications on Confluent Cloud details best practices for configuring, monitoring, and debugging Kafka clients.