[Yandex Cloud documentation](../../index.md) > [Yandex Managed Service for Apache Kafka®](../index.md) > [Concepts](index.md) > Connectors

# Connectors

Connectors are Kafka Connect components [built into Managed Service for Apache Kafka®](#supported) for streaming data between Apache Kafka® and other data systems. You can use a connector for continuous data migration to and from Managed Service for Apache Kafka® clusters. Data in connectors is handled through separate Kafka Connect *worker threads*. Learn more about Kafka Connect in [this Apache Kafka® guide](https://kafka.apache.org/42/kafka-connect/overview/).

Connectors perform the following functions:

* Connecting to Managed Service for Apache Kafka® clusters and other data stores.
* Reading and writing data.
* Managing data streaming.

For any type of connector, you can specify:

* Task limit that determines the number of workers running concurrently.
* Additional properties.

For a step-by-step guide on using connectors, see [Managing connectors](../operations/cluster-connector.md).

## Supported connectors {#supported-connectors}

### MirrorMaker {#mirrormaker}

{% note info %}

Managed Service for Apache Kafka® supports **MirrorMaker** version 2.

{% endnote %}

**MirrorMaker** is used for replicating Apache Kafka® topics between clusters.

A worker accesses the broker hosts of a Managed Service for Apache Kafka® cluster and replicates the topics specified in the connector filtering template. Depending on the connector's replication factor, it connects to one or more brokers.

Topic names in the target cluster cluster match those in the source cluster.

For more information about how MirrorMaker transfers data, see the [Apache Kafka® documentation](https://kafka.apache.org/42/operations/geo-replication-cross-cluster-data-mirroring/).

### S3 Sink {#s3-sink}

The **S3 Sink** connector is only used as a target for data export from Apache Kafka® topics to S3 storage.

The connector requests data from Apache Kafka® on a regular basis and uploads it to S3 storage. The data is split into chunks, which are S3 file objects. The size of each data chunk depends on the specified maximum number of records it contains.

For more on how S3 Sink transfers data, see the [connector's guide](https://github.com/aiven/s3-connector-for-apache-kafka).

### Iceberg Sink {#iceberg-sink}

The **Iceberg Sink** connector is used to transfer data from Apache Kafka® topics to Apache Iceberg™ tables.

For more on how Iceberg Sink transfers data, see the [connector guide](https://iceberg.apache.org/docs/nightly/kafka-connect/).


## Use cases {#examples}

* [Configuring Kafka Connect to work with a Managed Service for Apache Kafka® cluster](../tutorials/kafka-connect.md)
* [Migrating a database from a third-party Apache Kafka® cluster](../tutorials/kafka-connectors.md)
* [Moving data between Managed Service for Apache Kafka® clusters using Yandex Data Transfer](../tutorials/mkf-to-mkf-transfer.md)