# Kafka Connect

> For the complete documentation index, see [llms.txt](https://docs.redpanda.com/llms.txt). Component-specific: [streaming-full.txt](https://docs.redpanda.com/streaming-full.txt)

---
title: Kafka Connect
latest-operator-version: v26.1.4
# EOL = End-of-Life (support lifecycle status)
page-is-nearing-eol: "false"
page-is-past-eol: "true"
page-eol-date: December 22, 2024
latest-console-tag: v3.7.3
latest-connect-version: 4.93.0
docname: console/kafka-connect
page-component-name: streaming
page-version: "23.3"
page-component-version: "23.3"
page-component-title: Streaming
page-relative-src-path: console/kafka-connect.adoc
page-edit-url: https://github.com/redpanda-data/docs/edit/v/23.3/modules/manage/pages/console/kafka-connect.adoc
description: Connect one or more Kafka connect clusters with your Redpanda Console deployment.
page-git-created-date: "2023-06-02"
page-git-modified-date: "2024-02-26"
support-status: past end-of-life
---

<!-- Source: https://docs.redpanda.com/streaming/23.3/manage/console/kafka-connect.md -->

Redpanda Console provides a user interface that enables you to manage multiple Kafka connect clusters. You can inspect or patch connectors, restart/pause/resume their tasks, and also delete a connector. If you have configured more than one cluster, Redpanda Console will query all configured connect clusters for their status, so that you can have an overview across all your connect clusters.

## [](#configuration)Configuration

For each cluster you have to provide at least a unique name, the HTTP address of the cluster, and the authentication settings if required. The name can be any string of your choice that helps you to identify the connect cluster. The name has to be unique among the provided set of connect clusters though. You can view all available configuration options in the [Redpanda Console Configuration](https://docs.redpanda.com/streaming/23.3/reference/console/config/).

This sample configuration goes into the configuration file’s root level.

```yaml
connect:
  enabled: true
  clusters:
    - name: datawarehouse # Required field, will be used as identifier in the frontend
      url: http://dwh-connect.mycompany.com:8083
      tls:
        enabled: false # Trusted certs are still allowed by default
      username: admin
      # password: # Set using flag --connect.clusters.0.password=secret
    - name: analytics # Required field, will be used as identifier in the frontend
      url: http://analytics.mycompany.com:8083
      # No auth configured on that cluster, hence no username/password set
```

## Suggested labs

-   [Enable Unified Identity with Azure Entra ID for Redpanda and Redpanda Console](https://docs.redpanda.com/labs/docker-compose/oidc/)

[Search all labs](https://docs.redpanda.com/labs)