Overview of managing clusters in Console
To can add, update, and delete Kafka cluster configurations, go to Settings > Clusters. By default, only users belonging to the Admin group, or having theCan manage Cluster configurations
permission, will be able to view and manage the clusters.

Connect to a secure Kafka cluster
Conduktor leverages the default Apache Kafka Java Clients, and therefore we use the same configuration properties. When the Conduktor Console needs to connect to a secure Kafka cluster, you must specify the values from yourconfig.properties
file.
For example:
Connect to a Confluent cluster
Via your Confluent cluster dashboard, select the Clients tab within Data integration. Select Java as the language.


Connect to an Aiven cluster
When connecting to an Aiven cluster, you have two options.Option 1: With SSL
To connect to your Aiven cluster using SSL, you need to provide the Access Key, Access Certificate, and CA Certificate. You also need the cluster Bootstrap server, labelled as Service URI within the Aiven console.

Option 2: With SASL_SSL
To connect to your Aiven cluster using SASL_SSL, you need to provide the Bootstrap server labelled as Service URI, User, and Password. You can find these in the Aiven console.

Connect to a MSK cluster
For connecting to MSK, you first need to create an IAM user.


Connect to a Cloudera cluster
These instructions are for a setup with SASL_SSL and PLAIN mechanisms.
- To administer the Cloudera Kafka Cluster, you have to have a workload user with ownership of the Data Hub cluster configured. Make sure to note the username and password information of this user:

-
Download the certificates from Cloudera:
- Cloudera Certificates are CRT formatted files and need to be converted to a JKS file for console to connect. To convert the file please use the java keytool, command below is an example based on the screenshots above.
- In the Cloudera platform, open the firewalls for the Kafka brokers and schema registry.
- In Conduktor Console, go to Clusters, select the newly created Cloudera one and add the certs to your environment or click Upload certificate to manually upload them.
- Once you’ve added your certs to Console, configure the cluster in the below screenshot. Use the workload user and password from the first step.

Connect to a Google Cloud cluster
You can connect to Google Cloud Managed Service for Apache Kafka using the SASL_SSL protocol or the PLAIN mechanism with one of the following options.Option 1: Use a service account
Go to Google Cloud docs for instructions.Option 2: Use an access token
First, get an access token:- the access token is valid and has not expired
- the provided username matches the principal email that the access token is associated with
- the access token’s principal has the
managedkafka.clusters.connect
permission (included in roles/managedkafka.client) on the cluster