Yandex Cloud
Search
Contact UsGet started
  • Pricing
  • Customer Stories
  • Documentation
  • Blog
  • All Services
  • System Status
    • Featured
    • Infrastructure & Network
    • Data Platform
    • Containers
    • Developer tools
    • Serverless
    • Security
    • Monitoring & Resources
    • AI for business
    • Business tools
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Start testing with double trial credits
    • Cloud credits to scale your IT product
    • Gateway to Russia
    • Cloud for Startups
    • Center for Technologies and Society
    • Yandex Cloud Partner program
  • Pricing
  • Customer Stories
  • Documentation
  • Blog
© 2025 Direct Cursus Technology L.L.C.
Yandex Data Transfer
  • Available transfers
  • Getting started
    • All tutorials
      • MySQL® to Apache Kafka®
      • MySQL® to YDS
      • PostgreSQL to Apache Kafka®
      • PostgreSQL to YDS
      • YDB to Apache Kafka®
      • YDB and delivery to YDS
  • Troubleshooting
  • Access management
  • Pricing policy
  • Terraform reference
  • Monitoring metrics
  • Audit Trails events
  • Public materials

In this article:

  • Required paid resources
  • Getting started
  • Set up your transfer
  • Activate the transfer
  • Test the replication process
  • Delete the resources you created
  1. Tutorials
  2. Change data capture and delivery to the queue
  3. MySQL® to YDS

MySQL® change data capture and delivery to YDS

Written by
Yandex Cloud
Updated at November 26, 2025
  • Required paid resources
  • Getting started
  • Set up your transfer
  • Activate the transfer
  • Test the replication process
  • Delete the resources you created

You can track data changes in a Managed Service for MySQL® source cluster and send them to a Data Streams target cluster using change data capture (CDC).

To set up CDC using Data Transfer:

  1. Set up your transfer.
  2. Activate the transfer.
  3. Test the replication process.

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

Required paid resourcesRequired paid resources

  • Managed Service for MySQL® cluster: computing resources allocated to hosts, size of storage and backups (see Managed Service for MySQL® pricing).

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

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

  • Managed Service for YDB database. Its pricing is based on deployment mode:

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

    See Managed Service for YDB pricing.

  • Data Streams: 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.

    See Data Streams pricing.

Getting startedGetting started

Set up the infrastructure:

Manually
Terraform
  1. Create a Managed Service for MySQL® source cluster in any applicable configuration with publicly available hosts and the following settings:

    • DB name: db1
    • Username: mmy-user
  2. Grant the user the REPLICATION CLIENT and REPLICATION SLAVE admin privileges.

  3. Set up security groups and make sure they allow cluster connections.

  4. Create a Managed Service for YDB database named ydb-example in any suitable configuration.

  5. Create a service account named yds-sa with the yds.editor role. The transfer will use it to access Data Streams.

  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 mysql-yds.tf configuration file to the same working directory.

    This file describes:

    • Network.
    • Subnet.
    • Security group required for cluster connection.
    • Managed Service for MySQL® source cluster.
    • Managed Service for YDB database.
    • Service account to use for Data Streams access.
    • Source endpoint.
    • Transfer.
  6. In mysql-yds.tf, specify the MySQL® user password.

  7. Make sure the Terraform configuration files are correct using this command:

    terraform validate
    

    Terraform will show any errors found in your configuration 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.

Set up your transferSet up your transfer

  1. Create a data stream in Data Streams named mpg-stream.

  2. Connect to the Managed Service for MySQL® cluster, create a table named measurements in the db1 database, and populate it with data:

    CREATE TABLE measurements (
        device_id varchar(200) NOT NULL,
        datetime timestamp NOT NULL,
        latitude real NOT NULL,
        longitude real NOT NULL,
        altitude real NOT NULL,
        speed real NOT NULL,
        battery_voltage real,
        cabin_temperature real NOT NULL,
        fuel_level real,
        PRIMARY KEY (device_id)
    );
    INSERT INTO measurements VALUES
        ('iv9a94th6rzt********', '2022-06-05 17:27:00', 55.70329032, 37.65472196,  427.5,    0, 23.5, 17, NULL),
        ('rhibbh3y08qm********', '2022-06-06 09:49:54', 55.71294467, 37.66542005, 429.13, 55.5, NULL, 18, 32);
    
  3. Create a target endpoint of the Data Streams type with the following settings:

    • Database: ydb-example
    • Stream: mpg-stream
    • Service account: yds-sa
  4. Create a source endpoint and transfer:

    Manually
    Terraform
    1. Create a source endpoint of the MySQL® type and specify these cluster connection settings in it:

      • Connection type: Managed Service for MySQL cluster
      • Managed Service for MySQL cluster: <source_cluster_name> from the drop-down list.
      • Database: db1
      • User: mmy-user
      • Password: mmy-user password.
    2. Create a transfer of the Replication type that will use the new endpoints.

    1. In the mysql-yds.tf file, specify these variables:

      • yds_endpoint_id: ID of the target endpoint.
      • transfer_enabled: Set to 1 to create a transfer.
    2. Make sure the Terraform configuration files are correct using this command:

      terraform validate
      

      Terraform will show any errors found in your configuration 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.

Activate the transferActivate the transfer

  1. Activate the transfer and wait for its status to change to Replicating.

Make sure the data from the source has been moved to the Data Streams stream:

Management console
AWS CLI
  1. In the management console, select Data Streams.
  2. Select the target stream from the list and navigate to  Data viewer.
  3. Make sure shard-000000 now contains messages with the source table rows. For a closer look at the messages, click .
  1. Install the AWS CLI.

  2. Configure the environment for Data Streams.

  3. Read the stream data using:

    • AWS CLI.
    • AWS SDK.

Test the replication processTest the replication process

  1. Connect to the source cluster.

  2. Add a new row to the measurements table:

    INSERT INTO measurements VALUES
        ('ad02l5ck6sdt********', '2022-06-05 17:27:00', 55.70329032, 37.65472196,  427.5,    0, 23.5, 19, 45);
    
  3. Make sure you can now see the new row in your data stream.

Delete the resources you createdDelete the resources you created

Note

Before deleting the created resources, deactivate the transfer.

Some resources are not free of charge. To avoid paying for them, delete the resources you no longer need:

  1. Delete the transfer.
  2. Delete the target endpoint.
  3. Delete the stream in Data Streams.

Delete the other resources depending on how you created them:

Manually
Terraform
  • Source endpoint.
  • Managed Service for MySQL®.
  • Managed Service for YDB database.
  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.

Was the article helpful?

Previous
MySQL® to Apache Kafka®
Next
PostgreSQL to Apache Kafka®
© 2025 Direct Cursus Technology L.L.C.