FAQ for Confluent Cloud¶
This topic provides answers to general Confluent Cloud questions.
- How do I sign up for Confluent Cloud?
- What cloud providers and regions are supported?
- How does pricing and billing work for Confluent Cloud?
- What version of Kafka does Confluent Cloud use?
- What client and protocol versions are supported?
- What security, compliance, and privacy features does Confluent Cloud provide?
- 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 and hostnames static?
- How do I connect Confluent Platform components to Confluent Cloud?
- How do I grant other users access to my cluster?
- Can I use the same user account for multiple Confluent Cloud organizations?
- Can I be auto-notified about failures or incidents?
- Can I maintain unlimited retention using log compacted topics with Confluent Cloud?
- Can I access broker logs?
- Are there topic or partition limits?
- Can I switch between Confluent Cloud cluster types?
- Can deleted Confluent Cloud components be restored?
- How do I change support plans?
- What are the recommended JVM settings for Java clients?
- Why do I see the same bootstrap server for different clusters?
- How do I access the Cloud Console?
- What web browsers does Cloud Console support?
- What user session timeouts does Cloud Console require?
- What domains does the Cloud Console require?
- Does Cloud Console have a built-in tutorial?
- How do I monitor cluster activity with Cloud Console?
- How do I view cluster details with Cloud Console?
- How do I change a cluster name with Cloud Console?
- How do I delete a cluster with Cloud Console?
- How do I create keys for a cluster with Cloud Console?
- How do I access notifications with Cloud Console?
- How do I access Confluent CLI and support from Cloud Console?
- How do I install the CLI from Cloud Console?
- How do I access support from Cloud Console?
- How do I access account and billing information?
- How do I change my password in Cloud Console?
- How do I view my organization bill and ID in Cloud Console?
- How do I add users in Cloud Console?
Following is a list of the cloud providers and the region and zones supported by Confluent Cloud.
If you don’t see your region listed, contact Confluent. Additional regions can be supported by request.
Following is a list of regions supported for AWS grouped by geographic region.
- af-south-1 (Cape Town) 
- ca-central-1 (Canada Central)
- me-south-1 (Bahrain)
- me-central-1 (UAE)
- sa-east-1 (São Paulo)
 (1, 2, 3, 4, 5, 6, 7, 8, 9)
Regions that host Confluent Cloud Enterprise Kafka clusters
Following is a list of regions supported for Azure grouped by geographic region.
- southafricanorth (Johannesburg)
- Asia Pacific:
- australiaeast (New South Wales)
- centralindia (Pune)
- eastasia (Hong Kong)
- japaneast (Japan East)
- koreacentral (Seoul)
- southeastasia (Singapore)
- canadacentral (Canada)
- uaenorth (Dubai)
- francecentral (France)
- germanywestcentral (Germany West Central)
- northeurope (Ireland)
- norwayeast (Oslo)
- swedencentral (Gävle)
- switzerlandnorth (Zurich)
- uksouth (London)
- westeurope (Netherlands)
- qatarcentral (Doha)
- South America:
- brazilsouth (Brazil South)
- United States:
- centralus (Iowa)
- eastus (Virginia)
- eastus2 (Virginia)
- southcentralus (South Central US)
- westus2 (Washington)
- westus3 (Phoenix)
Following is a list of regions supported for GCP grouped by geographic region.
- asia-east1 (Taiwan)
- asia-east2 (Hong Kong)
- asia-northeast1 (Tokyo)
- asia-northeast2 (Osaka)
- asia-northeast3 (Seoul)
- asia-south1 (Mumbai)
- asia-south2 (Delhi)
- asia-southeast1 (Singapore)
- asia-southeast2 (Jakarta)
- australia-southeast1 (Sydney)
- australia-southeast2 (Melbourne)
- europe-central2 (Warsaw)
- europe-north1 (Finland)
- europe-southwest1 (Madrid)
- europe-west1 (Belgium)
- europe-west2 (London)
- europe-west3 (Frankfurt)
- europe-west4 (Netherlands)
- europe-west6 (Zurich)
- europe-west8 (Milan)
- europe-west9 (Paris)
- europe-west12 (Turin)
- Middle East:
- me-west1 (Tel Aviv)
- me-central1 (Doha)
- North America:
- northamerica-northeast1 (Montreal)
- northamerica-northeast2 (Toronto)
- South America:
- southamerica-east1 (São Paulo)
- southamerica-west1 (Santiago)
- United States:
- us-central1 (Iowa)
- us-east1 (S. Carolina)
- us-east4 (N. Virginia)
- us-west1 (Oregon)
- us-west2 (Los Angeles)
- us-west4 (Las Vegas)
Confluent Cloud bills are based on the consumption of resources within your cloud organization. For detailed billing information, see Manage Billing in Confluent Cloud.
Confluent Cloud runs the latest version of Confluent Platform, including all released and to-be-released updates. See Confluent Platform and Apache Kafka versions for the Kafka version.
- 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.
Confluent’s product offerings are designed to support the needs of enterprise customers for security, compliance, and privacy. For information on compliance and security, see the Trust & Security page page.
See What specific security features does Confluent Cloud offer? for more details about security features.
- 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 for Dedicated clusters on AWS, Azure, and Google Cloud.
- 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.
In most cases, no. Because the cloud infrastructure used by Confluent Cloud does not guarantee static IP addresses or hostnames across cluster changes, DNS is used to provide a consistent address. The underlying IP addresses and hostnames might be stable for a period of time, but are subject to change at any time, so they should not be relied upon for any use.
Confluent provides egress public IP addresses that you can use for communicating between Kafka clusters (with public networking) in Confluent Cloud and external data sources and sinks. For more information, see Use Public Egress IP Addresses on Confluent Cloud for Connectors and Cluster Linking and Static public IP address for Confluent Cloud connectors.
- Planned changes to the list of public egress ip addresses is considered a Major Upgrade and we will follow the policy outlined in Major Upgrades for Confluent Cloud.
- In the event of an unplanned change, Confluent will send out notifications as soon as possible and that you may be required to take immediate action to update your firewall rules.
In addition, DNS resolution for each Kafka cluster follows a predictable pattern.
For example, if your cluster bootstrap URL is
pkc-12345.<region>.<cloud>.<tld> and the default broker prefix is used, then
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> ...
The following blogs describe how the common outbound proxies handle IP address changes:
Connection instructions vary by by Confluent Platform component.
See Connect Confluent Platform Components to Confluent Cloud for a list of topics.
Confluent provides a variety of ways to manage access to your data. See Manage Accounts and Access for Confluent Cloud for more information.
Yes. For details, see Manage Multiple Organizations in Confluent Cloud.
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. For more information, see Kafka topic configurations for all Confluent Cloud cluster types.
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 provides actionable operational metrics about your Confluent Cloud deployment. The Confluent Cloud Console shows cluster activity and usage relative to your cluster’s capacity. The Cloud Console also includes topic management and consumer lag monitoring. Build Kafka Client Applications on Confluent Cloud details best practices for configuring, monitoring, and debugging Kafka clients.
Yes, these are described in Kafka Cluster Types in Confluent Cloud. 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 upgrade a Basic cluster to single-zone Standard cluster. No other changes to cluster type (including downgrading a Standard cluster to Basic) are supported. For more information on cluster types, see Kafka Cluster Types in Confluent Cloud.
No. When you delete components from your Confluent Cloud account, they are permanently deleted and cannot be restored.
You can manage your support plan by clicking the help 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. See Confluent Support for Confluent Cloud for more information.
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.
There are two recommended JVM settings for Java clients:
- 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
For more on configuring Java clients, see Configure clients.
In the Confluent Cloud Console, you may see the same bootstrap server for different clusters. This is working as designed; it occurs because Confluent Cloud clusters are multi-tenant.
Access the Cloud Console at the following URL:
To access the console, you will be required to sign in to your Confluent Cloud account. You can sign up for a free account, if you don’t have an account.
The latest stable versions of the following web browsers are supported by Confluent Cloud Console:
Each time you access your Confluent Cloud account in the Cloud Console from a web browser, you will be required to sign in. There are limits on how long you can remained signed in to your account with and without activity. The limits are as follows:
- Idle timeout: If no activity is seen in the Cloud Console browser tab for 30 minutes, you will be logged out.
- Maximum timeout: You can be logged in to Confluent Cloud for a maximum of 8 hours. After 8 hours, you will be logged out and must sign in again. This is enforced regardless of activity.
These are default settings and cannot be configured or changed.
The Cloud Console requires access to the following domains to function properly:
- Access to static assets, such as fonts and images:
- Access to Stripe (payment info):
- Access to the Confluent Metrics API:
The following domains are not required for the Cloud Console to operate properly, but are recommended:
- Sentry, for debugging purposes:
- For access to on-page help:
The Confluent Cloud Console includes an in-product tutorial that guides you through the basic steps for setting up your environment. This tutorial enables you to practice configuring Confluent Cloud components from directly within the console. Sign in to the Cloud Console and follow the tutorial link or click the LEARN button in the console to start the tutorial.
You can monitor cluster activity and usage from the Clusters page within each of your environments. To view the page, sign in to Confluent Cloud, choose an environment, and the Clusters page displays.
On the navigation menu, choose Cluster Overvew > Cluster Settings to access the Cluster settings page. You can view the cloud type, provider, region, and zone availability details, and delete a cluster from the General tab of this page.
Hover on the Cluster ID, Bootstrap server, or REST endpoint properties to access a copy-to-clipboard button for your convenience. Paste these details when you are configuring, running commands, or troubleshooting your cluster.
For more information, see How to work with Kafka clusters.
The General tab of the Cluster settings page also enables you to edit the cluster name.
On the Cluster settings page, make sure the General tab is selected, and click the Edit icon.
Edit the cluster name in Cluster name field and click Save changes.
For more information, see How to work with Kafka clusters.
The Cluster settings page enables you to delete a cluster.
From the Cluster settings, make sure the General tab is selected, and click Delete cluster.
You are prompted to confirm the deletion.
For more information, see How to work with Kafka clusters.
To create and delete API keys for cluster resources, navigate to Cluster Overview and choose API keys. Select a key to edit its description. For more information, see Resource API keys.
Access the Manage notifications page by clicking the Alert bell icon in the upper right of the console. To learn more about notifications, see Notifications for Confluent Cloud.
See instructions to install and use the Confluent CLI, and access Confluent support and tools from options located at the bottom of the navigation menu.
Choose CLI and tools, located at the bottom of the navigation menu. Select the Confluent CLI tab for step-by-step instructions to install and access your Confluent Cloud environment with the Confluent CLI. For more information about how to install and use the Confluent CLI, see Confluent CLI.
To access Confluent support, choose Support located at the bottom of the navigation menu. The support plans display, with your current plan indicated. See Confluent Cloud support plans for details about the plans.
The Administration menu in the upper right enables you to access account and billing information, and create API access keys for the cloud account.
From the Administration menu, click Settings > Reset password.
An email will be sent to the email address associated with the account to reset your password.
From the Administration menu, click Billing & payment. The Billing page shows current accrued charges by selected environment and time period (year and month).
Click the Payment details & contacts tab to obtain your Cloud Organization ID, edit your billing information, add an address for tax purposes, or claim a Promo Code.
For more information, see the billing page.