Discuss with expertTry it for free
© 2026 Direct Cursus Technology L.L.C.

Delivering data from a Data Streams queue to Managed Service for Apache Kafka®

Written by
Updated at September 1, 2026
View in Markdown

With Data Transfer, you can deliver data from a stream in Data Streams to a Managed Service for Apache Kafka® cluster.

To transfer data:

  1. Set up a data stream in Data Streams.
  2. Prepare and activate the transfer.
  3. Test the transfer.

If you no longer need the resources you created, delete them.

  • Managed Service for YDB database (see Managed Service for YDB pricing). The cost depends on the deployment mode:

    • In serverless mode, you pay for data operations as well as the amount of stored data and backups.
    • In dedicated instance mode, you pay for the use of computing resources allocated to the database, storage size, and backups.

  • Data Streams (see Data Streams pricing). The cost depends on the pricing model:

    • Based on allocated resources: You pay a fixed hourly rate for the established throughput limit and message retention period, and additionally for the number of units of actually written data.
    • On-demand: You pay for the performed read/write operations, the amount of read or written data, and the actual storage used for messages that are still within their retention period.

  • Managed Service for Apache Kafka® cluster: computing resources allocated to hosts, storage and backup size (see Managed Service for Apache Kafka® pricing).

  • Public IP addresses if public access is enabled for cluster hosts (see Virtual Private Cloud pricing).

  • Each transfer: use of computing resources and the number of transferred data rows (see Data Transfer pricing).

Getting started

Set up your data delivery infrastructure:

  1. Create a Managed Service for YDB database of any suitable configuration.

  2. Create a service account and assign it the yds.editor role for the folder. The transfer will use it to access the data stream.

  3. Create a Managed Service for Apache Kafka® cluster of any suitable configuration with publicly accessible hosts.

    Note

    Public access to cluster hosts is required if you plan to connect to the cluster via the internet. This connection option is simpler and is recommended for the purposes of this guide. You can connect to non-public hosts as well but only from Yandex Cloud virtual machines located in the same cloud network as the cluster.

  4. In the Managed Service for Apache Kafka® cluster, create a topic named sensors.

  5. In the Managed Service for Apache Kafka® cluster, create a user with the ACCESS_ROLE_PRODUCER and ACCESS_ROLE_CONSUMER access permissions for the new topic.

  1. If you do not have Terraform yet, install it.

  2. Get the authentication credentials. You can add them to environment variables or specify them later in the provider configuration file.

  3. Configure and initialize a provider. There is no need to create a provider configuration file manually, you can download it.

  4. Place the configuration file in a separate working directory and specify the parameter values. If you did not add the authentication credentials to environment variables, specify them in the configuration file.

  5. Download the yds-to-kafka.tf configuration file to the same working directory.

    This file describes:

    • Network.
    • Subnet.
    • Security group and rules for connection to a Managed Service for Apache Kafka® cluster.
    • Service account.
    • Managed Service for YDB database.
    • Managed Service for Apache Kafka® cluster.
    • Managed Service for Apache Kafka® topic named sensors.
    • Managed Service for Apache Kafka® user with the ACCESS_ROLE_PRODUCER and ACCESS_ROLE_CONSUMER access permissions for the sensors topic.
    • Source endpoint.
    • Target endpoint.
    • Transfer.

  6. In the yds-to-kafka.tf file, specify the following settings:

    • folder_id: Folder ID.
    • ydb_name: Managed Service for YDB database name.
    • stream_name: Data Streams stream name.
    • mkf_version: Apache Kafka® cluster version.
    • mkf_user_name: Managed Service for Apache Kafka® cluster user name.
    • mkf_user_password: User password in the Managed Service for Apache Kafka® cluster.

  7. Validate your Terraform configuration files using this command:

    terraform validate

    Terraform will display any configuration errors detected in your files.

  8. Create the required infrastructure:

    1. Run this command to view the planned changes:

      terraform plan

      If you described the configuration correctly, the terminal will display a list of the resources to update and their parameters. This is a verification step that does not apply changes to your resources.

    2. If everything looks correct, apply the changes:

      1. Run this command:

        terraform apply

      2. Confirm updating the resources.

      3. Wait for the operation to complete.

    All the required resources will be created in the specified folder. You can check resource availability and their settings in the management console.

Create a data stream in Data Streams

Create a data stream in Data Streams.

Prepare and activate a transfer

  1. Create a Data Streams source endpoint.

    • Database type: Yandex Data Streams.

    • Endpoint parameters:

      • Connection settings:

        • Connection type: Select Managed Service for YDB database.
        • Database: Select the previously created Managed Service for YDB database from the list.
        • Stream: Specify the name of the Data Streams data stream you created.
        • Service account: Select the previously created service account with the yds.editor role.

      • Advanced settings:

        • Conversion rules: JSON.
        • Data scheme: JSON specification:

        Fill in the data schema:

        Data schema
            [
        {
            "name": "device_id",
            "type": "string"
        },
        {
            "name": "datetime",
            "type": "datetime"
        },
        {
            "name": "latitude",
            "type": "double"
        },
        {
            "name": "longitude",
            "type": "double"
        },
        {
            "name": "altitude",
            "type": "double"
        },
        {
            "name": "speed",
            "type": "double"
        },
        {
            "name": "battery_voltage",
            "type": "any"
        },
        {
            "name": "cabin_temperature",
            "type": "double"
        },
        {
            "name": "fuel_level",
            "type": "any"
        }
    ]

  2. Create a target endpoint in Managed Service for Apache Kafka®.

    • Database type: Kafka.

    • Endpoint parameters:

      • Connection settings:

        • Connection type: Select Managed Service for Apache Kafka cluster.
        • Managed Service for Apache Kafka cluster: Select your previously created Managed Service for Apache Kafka® cluster from the list.
        • Authentication: Select SASL and specify the credentials of the Apache Kafka® user you created.
        • Topic: Select Topic full name.
        • Topic full name: Set it to sensors.

  3. Create a transfer of the Replication type that will use the new endpoints.

  4. Activate the transfer.

  1. In the data-transfer-ydb-mkf.tf file, set the transfer_enabled variable to 1 to create your endpoints and transfer.

  2. Validate your Terraform configuration files using this command:

    terraform validate

    Terraform will display any configuration errors detected in your files.

  3. Create the required infrastructure:

    1. Run this command to view the planned changes:

      terraform plan

      If you described the configuration correctly, the terminal will display a list of the resources to update and their parameters. This is a verification step that does not apply changes to your resources.

    2. If everything looks correct, apply the changes:

      1. Run this command:

        terraform apply

      2. Confirm updating the resources.

      3. Wait for the operation to complete.

    The transfer will be activated automatically upon creation.

Test the transfer

  1. Wait for the transfer status to change to Replicating.

  2. Send test data to the stream in Data Streams:

    {
    "device_id":"iv9a94th6rzt********",
    "datetime":"2020-06-05T17:27:00",
    "latitude":"55.70329032",
    "longitude":"37.65472196",
    "altitude":"427.5",
    "speed":"0",
    "battery_voltage":"23.5",
    "cabin_temperature":"17",
    "fuel_level":null
}

  3. Make sure the data has been transferred to the sensors topic in the Managed Service for Apache Kafka® cluster:

    1. Get an SSL certificate to connect to the Managed Service for Apache Kafka® cluster.
    2. Install kafkactl:
    3. Run the command for receiving messages from a topic.

Delete the resources you created

To minimize resource consumption, delete the resources you no longer need:

  1. Delete the Data Streams data stream.

  2. Delete the other resources depending on how you created them:

    1. In the terminal window, go to the directory containing the infrastructure plan.

      Warning

      Make sure the directory has no Terraform manifests with the resources you want to keep. Terraform deletes all resources that were created using the manifests in the current directory.

    2. Delete resources:

      1. Run this command:

        terraform destroy

      2. Confirm deleting the resources and wait for the operation to complete.

      All the resources described in the Terraform manifests will be deleted.

Previous
Saving a data stream from Data Streams to Managed Service for ClickHouse®
Next
Delivering data from a Data Streams queue to Managed Service for YDB using Data Transfer