Does Kafka Confluent Edition support sending and receiving messages over HTTPS?
Yes. Confluent supports HTTPS messaging through the Kafka REST Proxy. HTTPS requests are forwarded to the Kafka REST Proxy, which then forwards them to Kafka, rather than sending them directly.
Does Kafka Confluent Edition support bidirectional TLS access?
The Kafka REST Proxy supports only unidirectional TLS. Bidirectional TLS is not supported.
Specifically, bidirectional TLS is not supported between the Kafka REST Proxy and Kafka, or between clients and the frontend Server Load Balancer (SLB) for the Kafka REST Proxy.
What should I know when installing and using Kafka Confluent Edition?
The SLB domain name maps to the Kafka REST Proxy. Clients can connect using this domain name directly. For more information, see Network Access and Security Settings.
You can download the TLS certificate from the console.
VPC access: The service is accessible as long as the network is reachable. No cross-region or cross-account restrictions apply.
When Kafka brokers reach their capacity limit, you can perform horizontal scale-out to add replicas. Vertical scale-out is not supported.
When you purchase a cluster, under Compute Resource Configuration, each Kafka Broker replica defaults to 20 CUs / 800 GB, and you can set the number of replicas. The Component Resource Configuration includes components such as ZooKeeper, ControlCenter, SchemaRegistry, Connect, KsqlDB, and Kafka REST Proxy. To add more resources, request a cluster scale-out after purchase.
For resource assessment guidelines, see Cluster Resource Assessment.
What do I do if an SLB quota error occurs when deploying Confluent?
Deploying a Confluent instance requires multiple SLBs. If you encounter an SLB quota error, increase your SLB quota in Quota Center—for example, to 200—and then redeploy. Visit SLB Quota Center.
On the Quota Center page, on the General Quota tab, find the slb_quota_instances_num quota item. In the Actions column, click Apply to request a quota increase.