Yandex Cloud
Search
Contact UsGet started
  • Blog
  • Pricing
  • Documentation
  • All Services
  • System Status
    • Featured
    • Infrastructure & Network
    • Data Platform
    • Containers
    • Developer tools
    • Serverless
    • Security
    • Monitoring & Resources
    • ML & AI
    • Business tools
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Customer Stories
    • Cloud credits to scale your IT product
    • Gateway to Russia
    • Cloud for Startups
    • Education and Science
    • Yandex Cloud Partner program
  • Blog
  • Pricing
  • Documentation
© 2025 Direct Cursus Technology L.L.C.
Yandex Object Storage
    • All tutorials
    • Getting statistics on object queries with S3 Select
    • Getting website traffic statistics with S3 Select
    • Getting statistics on object queries using Yandex Query
    • Generating a resource-by-resource cost breakdown report using S3 Select
    • Server-side encryption
    • Integrating an L7 load balancer with CDN and Object Storage
    • Blue-green and canary deployment of service versions
    • Analyzing logs in DataLens
    • Mounting buckets to the file system of Yandex Data Processing hosts
    • Using Object Storage in Yandex Data Processing
    • Importing data from Object Storage, processing and exporting to Managed Service for ClickHouse®
    • Mounting a bucket as a disk in Windows
    • Migrating data from Yandex Data Streams using Yandex Data Transfer
    • Using hybrid storage in Yandex Managed Service for ClickHouse®
    • Loading data from Yandex Managed Service for OpenSearch to Yandex Object Storage using Yandex Data Transfer
    • Automatically copying objects from one bucket to another
    • Recognizing audio files in a bucket on a regular basis
    • Training a model in Yandex DataSphere on data from Object Storage
    • Connecting to Object Storage from VPC
    • Migrating data to Yandex Managed Service for PostgreSQL using Yandex Data Transfer
    • Uploading data to Yandex Managed Service for Greenplum® using Yandex Data Transfer
    • Uploading data to Yandex Managed Service for ClickHouse® using Yandex Data Transfer
    • Uploading data to Yandex Managed Service for YDB using Yandex Data Transfer
    • Exchanging data between Yandex Managed Service for ClickHouse® and Yandex Data Processing
    • Uploading data from Yandex Managed Service for YDB using Yandex Data Transfer
    • Hosting a static Gatsby website in Object Storage
    • Migrating a database from Managed Service for PostgreSQL to Object Storage
    • Exchanging data between Yandex Managed Service for ClickHouse® and Yandex Data Processing
    • Importing data from Yandex Managed Service for PostgreSQL to Yandex Data Processing using Sqoop
    • Importing data from Yandex Managed Service for MySQL® to Yandex Data Processing using Sqoop
    • Migrating data from Yandex Object Storage to Yandex Managed Service for MySQL® using Yandex Data Transfer
    • Migrating a database from Yandex Managed Service for MySQL® to Yandex Object Storage
    • Exporting Greenplum® data to a cold storage in Yandex Object Storage
    • Loading data from Yandex Direct to a Yandex Managed Service for ClickHouse® data mart using Yandex Cloud Functions, Yandex Object Storage, and Yandex Data Transfer
    • Migrating data from Elasticsearch to Yandex Managed Service for OpenSearch
    • Uploading Terraform states to Object Storage
    • Locking Terraform states using Managed Service for YDB
    • Visualizing Yandex Query data
    • Publishing game updates
    • VM backups using Hystax Acura
    • Backing up to Object Storage with CloudBerry Desktop Backup
    • Backing up to Object Storage with Duplicati
    • Backing up to Object Storage with Bacula
    • Backing up to Yandex Object Storage with Veeam Backup
    • Backing up to Object Storage with Veritas Backup Exec
    • Managed Service for Kubernetes cluster backups in Object Storage
    • Developing a custom integration in API Gateway
    • URL shortener
    • Storing application runtime logs
    • Developing a skill for Alice and a website with authorization
    • Creating an interactive serverless application using WebSocket
    • Deploying a web application using the Java Servlet API
    • Developing a Telegram bot
    • Replicating logs to Object Storage using Fluent Bit
    • Replicating logs to Object Storage using Data Streams
    • Uploading audit logs to ArcSight SIEM
    • Exporting audit logs to SIEM Splunk systems
    • Creating an MLFlow server for logging experiments and artifacts
    • Operations with data using Yandex Query
    • Federated data queries using Query
    • Recognizing text in image archives using Vision OCR
    • Converting a video to a GIF in Python
    • Automating tasks using Managed Service for Apache Airflow™
    • Processing files with usage details in Yandex Cloud Billing
    • Deploying a web app with JWT authorization in API Gateway and authentication in Firebase
    • Searching for Yandex Cloud events in Yandex Query
    • Searching for Yandex Cloud events in Object Storage
    • Creating an external table from a bucket table using a configuration file
    • Migrating databases from Google BigQuery to Managed Service for ClickHouse®
  • Terraform reference
  • Monitoring metrics
  • Audit Trails events
  • Bucket logs
  • Release notes
  • FAQ

In this article:

  • Required paid resources
  • Getting started
  • Prepare the test data
  • Prepare and activate your transfer
  • Test the transfer
  • Delete the resources you created
  1. Tutorials
  2. Migrating data from Yandex Object Storage to Yandex Managed Service for MySQL® using Yandex Data Transfer

Migrating data from Object Storage to Yandex Managed Service for MySQL® using Yandex Data Transfer

Written by
Yandex Cloud
Updated at May 7, 2025
  • Required paid resources
  • Getting started
  • Prepare the test data
  • Prepare and activate your transfer
  • Test the transfer
  • Delete the resources you created

With Data Transfer, you can transfer data from an Object Storage object storage to a Managed Service for MySQL® target cluster.

To transfer data:

  1. Prepare the test data.
  2. Prepare and activate your transfer.
  3. Test the transfer.

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

Required paid resourcesRequired paid resources

The support cost includes:

  • Object Storage bucket fee: Storing data and performing operations with it (see Object Storage pricing).
  • Managed Service for MySQL® cluster fee: Using computing resources allocated to hosts and disk space (see Managed Service for MySQL® pricing).
  • Fee for using public IP addresses if public access is enabled for cluster hosts (see Virtual Private Cloud pricing).
  • Per-transfer fee: Using computing resources and the number of transferred data rows (see Data Transfer pricing).

Getting startedGetting started

Set up your infrastructure:

Manually
Terraform
  1. Create an Yandex Object Storage bucket.

  2. Create a service account named storage-viewer with the storage.viewer role. The transfer will use it to access the bucket.

  3. Create a static access key for the storage-viewer service account.

  4. Create a target Managed Service for MySQL® cluster of any suitable configuration with the following settings:

    • DB name: db1
    • Username: mmy-user
    • Password: <user_password>
  5. Assign the MySQL® user the ALL_PRIVILEGES role for the target database.

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

    This file describes:

    • Network.
    • Subnet.
    • Security group and the rule required to connect to a Managed Service for MySQL® cluster.
    • Service account for creating and accessing the bucket
    • Yandex Lockbox secret which will store the static key of the service account to configure the source endpoint.
    • Source Object Storage bucket.
    • Target Managed Service for MySQL® cluster.
    • Target endpoint.
    • Transfer.
  6. Specify the following in the data-transfer-objs-mmy.tf file:

    • folder_id: ID of the folder to create the resources in.
    • bucket_name: Bucket name consistent with the naming conventions.
    • mmy_password: MySQL® user password.
  7. Make sure the Terraform configuration files are correct using this command:

    terraform validate
    

    If there are any errors in the configuration files, Terraform will point them out.

  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 test dataPrepare the test data

  1. Create a data.csv text file on the running instance and fill it with test data. As an example, we will use readings returned by car sensors:

    1;99101;2022-06-05 17:27:00;55.70329032;37.65472196;427.5;52.3;23.5;17.;52.
    2;95106;2022-06-06 09:49:54;55.71294467;37.66542005;429.13;55.5;21.;18.;32.
    3;117890;2023-06-07 06:21:29;55.71294467;37.66542005;429.13;56.2;20.;18.7;45.
    4;99101;2022-06-07 08:15:32;55.29194467;37.66542005;429.13;59.1;21.;18.;20.
    
  2. Upload the file to the Object Storage bucket you created earlier.

Prepare and activate your transferPrepare and activate your transfer

  1. Create a source endpoint with the following settings:

    • Database type: Object Storage.

    • Bucket: Bucket name in Object Storage.

    • Access Key ID: Public part of the service account static key. If you created your infrastructure with Terraform, copy the key value from the Yandex Lockbox secret.

    • Secret Access Key: Private part of the service account’s static key. If you created your infrastructure with Terraform, copy the key value from the Yandex Lockbox secret.

    • Endpoint: https://storage.yandexcloud.net.

    • Region: ru-central1.

    • Data format: CSV.

    • Delimiter: Semicolon (;).

    • Table: measurements.

    • Add system columns: Disable this option.

    • Result table schema: Select Manual and specify field names and data types:

      • id: INT64, Key property

      • device_id: INT32

      • datetime: DATETIME

        Note

        The target endpoint writes DATETIME type data in the UTC+0 time zone.

      • latitude: DOUBLE

      • longitude: DOUBLE

      • altitude: DOUBLE

      • speed: DOUBLE

      • battery_voltage: DOUBLE

      • cabin_temperature: DOUBLE

      • fuel_level: DOUBLE

    Leave the default values for the other properties.

  2. Create an endpoint for the target and transfer:

    Manually
    Terraform
    1. Create a target endpoint:

      • Database type: MySQL

      • Endpoint parameters:

        • Connection settings:
          • Connection type: Managed Service for MySQL cluster

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

    2. Create a transfer of the Snapshot and replication type that will use the created endpoints.

    3. Activate your transfer.

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

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

      terraform validate
      

      If there are any errors in the configuration files, Terraform will point them out.

    3. Create the required infrastructure for the transfer:

      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.

      Once created, your transfer will be activated automatically.

Test the transferTest the transfer

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

  2. Connect to the target Managed Service for MySQL® cluster’s database.

  3. To make sure the data was successfully transferred, run this request:

    SELECT * FROM db1.measurements;
    
    Response example
     id | device_id |     datetime        |  latitude | longitude | altitude | speed | battery_voltage | cabin_temperature | fuel_level
    ----------------+---------------------+-----------+-----------+----------+-------+-----------------+-------------------+----------+
      1 |     99101 | 2022-06-05T17:27:00 | 55.703289 |  37.66542 |   427.50 | 52.29 |            23.5 |              17.0 |     52.0 |
      2 |     95106 | 2022-06-06T09:49:54 | 55.712944 |  37.66542 |   429.13 | 55.50 |            21.0 |              18.0 |     32.0 |
      3 |    117890 | 2023-06-07T06:21:29 | 55.712944 |  37.66542 |   429.13 | 56.20 |            20.0 |              18.7 |     45.0 |
      4 |     99101 | 2022-06-05 17:27:00 | 55.291944 |  37.66542 |   429.13 | 59.09 |            21.0 |              18.0 |     20.0 |
    
  4. Create the data2.csv text file containing new data:

    7;95106;2022-06-07 09:54:32;47.71294467;37.66542005;429.13;62.2;21.;20.4;27.
    9;117890;2022-06-07 11:56:27;52.71294467;37.66542005;429.13;65.5;19.;19.;38.
    10;117890;2022-06-07 12:36:27;57.71294467;37.66542005;429.13;72.1;19.;20.;25.
    11;99101;2022-06-07 15:22:27;59.71294467;37.66542005;429.13;35.5;19.;18.;12.
    
  5. Upload the file to the Object Storage bucket for transfer.

  6. Make sure the new data has been added to the db1.measurements table of the MySQL® target database.

Delete the resources you createdDelete the resources you created

Note

Before deleting the resources you created, 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.

Delete the other resources depending on how they were created:

Manually
Terraform
  1. Delete the source endpoint.
  2. Delete the Object Storage bucket.
  3. Delete the Managed Service for MySQL® cluster.
  4. If you 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
Importing data from Yandex Managed Service for MySQL® to Yandex Data Processing using Sqoop
Next
Migrating a database from Yandex Managed Service for MySQL® to Yandex Object Storage
© 2025 Direct Cursus Technology L.L.C.