Yandex Cloud
Search
Contact UsTry it for free
  • Customer Stories
  • Documentation
  • Blog
  • All Services
  • System Status
  • Marketplace
    • Featured
    • Infrastructure & Network
    • Data Platform
    • AI for business
    • Security
    • DevOps tools
    • Serverless
    • Monitoring & Resources
  • 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
    • Price calculator
    • Pricing plans
  • Customer Stories
  • Documentation
  • Blog
© 2026 Direct Cursus Technology L.L.C.
Yandex Data Transfer
  • Available transfers
  • Getting started
    • All tutorials
      • MySQL® to Object Storage
      • PostgreSQL to Object Storage
      • OpenSearch to Object Storage
      • Managed Service for YDB to Object Storage
      • Replicating logs to Object Storage using Data Streams
      • Replicating logs to Object Storage using Fluent Bit
  • Troubleshooting
  • Access management
  • Pricing policy
  • Terraform reference
  • Monitoring metrics
  • Audit Trails events
  • Public materials

In this article:

  • Required paid resources
  • Getting started
  • Prepare the source cluster
  • Set up and activate the transfer
  • Test your transfer
  • Delete the resources you created
  1. Tutorials
  2. Uploading data to Object Storage
  3. MySQL® to Object Storage

Loading data from MySQL® to Yandex Object Storage

Written by
Yandex Cloud
Updated at January 15, 2026
  • Required paid resources
  • Getting started
  • Prepare the source cluster
  • Set up and activate the transfer
  • Test your transfer
  • Delete the resources you created

Data Transfer enables you to transfer data from a Managed Service for MySQL® source cluster to Yandex Object Storage.

To transfer data:

  1. Prepare the source cluster.
  2. Set up and activate the transfer.
  3. Test your transfer.

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, storage and backup size (see Managed Service for MySQL® pricing).
  • Public IP addresses if public access is enabled for cluster hosts (see Virtual Private Cloud pricing).
  • Object Storage bucket: Use of storage, data operations (see Object Storage pricing).

Getting startedGetting started

Set up the infrastructure:

Manually
Terraform
  1. Create a Managed Service for MySQL® source cluster with any suitable configuration.
  2. Create a bucket in Yandex Object Storage.
  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 data-transfer-mmy-objs.tf configuration file to the same working directory.

    This file describes:

    • Network.
    • Subnet.
    • Security group and the rule permitting access to the Managed Service for MySQL® cluster.
    • Managed Service for MySQL® source cluster.
    • Service account with the editor, storage.editor, and storage.uploader roles.
    • Object Storage bucket.
    • Source endpoint.
    • Transfer.
  6. In the data-transfer-mmy-objs.tf file, specify the following:

    • folder_id: ID of the folder for the new resources.

    • sa_name: Name of the service account for creating a bucket and for use in the target endpoint.

    • bucket_name: Object Storage bucket name.

    • Managed Service for MySQL® source cluster parameters to use for the source endpoint:

      • source_mysql_version: MySQL® version.
      • source_db_name: Database name.
      • source_user and source_password: Database owner username and password.
    • transfer_enabled: Set to 0 to ensure that no transfer is created before you manually create the target endpoint.

  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.

Prepare the source clusterPrepare the source cluster

  1. If you created the infrastructure manually, set up your source cluster.

  2. Connect to the Managed Service for MySQL® source cluster.

  3. Populate the database with test data. In this example, we will use a table containing information from car sensors.

    Create a table:

    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)
    );
    

    Populate the table with data:

    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);
    

Set up and activate the transferSet up and activate the transfer

  1. Create a target endpoint:

    • Database type: Object Storage.

    • Endpoint settings:

      • Connection settings:

        • Bucket: Specify the Object Storage bucket name.

        • Service account: Select or create a service account with the storage.uploader role.

      • Folder name: measurements.

  2. Create a source endpoint and transfer:

    Manually
    Terraform
    1. Create a source endpoint:

      • Database type: MySQL.

      • Endpoint parameters:

        • Connection settings:

          • Connection type: Managed Service for MySQL cluster.

            Select your source cluster from the list and specify its connection settings.

        • Included tables, Excluded tables: Regular expressions for the tables you want to transfer and for those you want to ignore. These parameters are optional.

    2. Create a Snapshot-type transfer configured to use the new endpoints.

    3. Activate the transfer.

    1. In the data-transfer-mmy-objs.tf file, specify the following variables:

      • target_endpoint_id: ID of the target endpoint.
      • transfer_enabled: 1 to create a transfer.
      • include_tables_regex, exclude_tables_regex: Regular expressions for the tables you want to transfer and for those you want to ignore. These variables are optional.
    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 activate automatically upon creation.

Test your transferTest your transfer

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

  2. Make sure the data has been transferred from the Managed Service for MySQL® source cluster to the Object Storage bucket:

    1. In the management console, select the folder containing your bucket.
    2. In the list of services, select Object Storage.
    3. Select the bucket from the list.
    4. Navigate to the Objects tab.
    5. Make sure the Object Storage bucket contains the measurements directory with the <source_cluster_database_name>_measurements object with test data.

Delete the resources you createdDelete the resources you created

Note

Before deleting the resources, deactivate the transfer.

To reduce the consumption of resources you do not need, delete them:

  1. Delete the transfer.

  2. Delete the target endpoint.

  3. Delete other resources using the same method used for their creation:

    Manually
    Terraform
    1. Delete the source endpoint.

    2. Delete the Object Storage bucket.

    3. Delete the Managed Service for MySQL® cluster.

    4. If you have created a service account when creating the target endpoint, delete it.

    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
OpenSearch in ClickHouse®
Next
PostgreSQL to Object Storage
© 2026 Direct Cursus Technology L.L.C.