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 Data Transfer
  • Available transfers
  • Getting started
    • All tutorials
      • Greenplum® to ClickHouse®
      • MySQL® in ClickHouse®
      • Yandex Metrica to ClickHouse®
      • PostgreSQL in ClickHouse®
      • Greenplum® to PostgreSQL
      • Object Storage in MySQL®
      • Object Storage to PostgreSQL
      • Object Storage to Greenplum®
      • Yandex Direct to ClickHouse®
      • Object Storage in ClickHouse®
      • Object Storage to YDB
      • YDB to ClickHouse®
      • OpenSearch in ClickHouse®
  • Troubleshooting
  • Access management
  • Terraform reference
  • Monitoring metrics
  • Audit Trails events
  • Public materials

In this article:

  • Required paid resources
  • Getting started
  • Prepare the test data
  • Prepare and activate your transfer
  • Test the transfer
  • Test the copy process
  • Test the replication process
  • Delete the resources you created
  1. Tutorials
  2. Uploading data to data marts
  3. Object Storage to YDB

Loading data from Object Storage to a YDB data mart

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
    • Test the copy process
    • Test the replication process
  • Delete the resources you created

You can migrate data from Object Storage to the Managed Service for YDB table using Data Transfer. To do this:

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

  • Per-transfer fee: Using computing resources and the number of transferred data rows (see Data Transfer pricing).

  • Fee for the Managed Service for YDB database. The charge depends on the usage mode:

    • For the serverless mode, you pay for data operations and the amount of stored data.
    • For the dedicated instance mode, you pay for the use of computing resources, dedicated DBs, and disk space.

    Learn more about the Managed Service for YDB pricing plans.

Getting startedGetting started

Set up your infrastructure:

Manually
Using Terraform
  1. Create a Managed Service for YDB database in any suitable configuration.

  2. If you selected Dedicated DB mode, create and configure a security group in the network hosting the DB.

  3. Create an Object Storage bucket.

  4. Create a service account named s3-ydb-account with the storage.editor and ydb.editor roles. The transfer will use it to access the bucket and database.

  5. Create a static access key for s3-ydb-account.

  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 object-storage-to-ydb.tf configuration file to the same working directory.

    This file describes:

    • Service account to use when working with the Managed Service for YDB bucket and database.
    • Yandex Lockbox secret which will store the static key of the service account to configure the source endpoint.
    • Source Object Storage bucket.
    • Managed Service for YDB target cluster.
    • Target endpoint.
    • Transfer.
  6. In the object-storage-to-ydb.tf file, specify the values of the following variables:

    • folder_id: Cloud folder ID, same as in the provider settings.
    • bucket_name: Bucket name consistent with the naming conventions.
  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. Prepare two CSV files with test data:

    • demo_data1.csv:

      1,Anna
      2,Robert
      3,Umar
      4,Algul
      5,Viktor
      
    • demo_data2.csv:

      6,Maria
      7,Alex
      
  2. Upload the demo_data1.csv file to the Object Storage bucket.

Prepare and activate your transferPrepare and activate your transfer

  1. Create a source endpoint of the Object Storage type 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 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: Comma (,).

    • Table: table1.

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

      • Id: Int64
      • Name: UTF8

    Leave the default values for the other properties.

  2. Create a target endpoint and transfer:

    Manually
    Using Terraform
    1. Create a target endpoint of the YDB type and specify the cluster connection settings in it:

      • Database: Select the YDB database from the list.
      • Service account ID: Select the service account named s3-ydb-account.
    2. Create a transfer of the Snapshot and replication type that will use the created endpoints.

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

    1. In the object-storage-to-ydb.tf file, specify the following settings:

      • source_endpoint_id: Source endpoint ID.
      • 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:

      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.

    4. The transfer will be activated automatically. Wait for its status to change to Replicating.

Test the transferTest the transfer

Check the transfer performance by testing the copy and replication processes.

Test the copy processTest the copy process

Management console
CLI
  1. In the management console, select the folder with the DB you need.
  2. From the list of services, select Managed Service for YDB.
  3. Select the database from the list.
  4. Navigate to the Navigation tab.
  5. Make sure the Managed Service for YDB database contains a table named table1 with the test data.
  1. Connect to the Managed Service for YDB database.

  2. Run this request:

    SELECT * FROM table1;
    
    Response example
    Id |   Name   |   __file_name    | __row_index 
    ---+----------+------------------+-------------
     1 | "Anna"   | "demo_data1.csv" | 1 
     2 | "Robert" | "demo_data1.csv" | 2 
     3 | "Umar"   | "demo_data1.csv" | 3 
     4 | "Algul"  | "demo_data1.csv" | 4 
     5 | "Viktor" | "demo_data1.csv" | 5 
    

Test the replication processTest the replication process

  1. Upload the demo_data2.csv file to the Object Storage bucket.

  2. Make sure the data from demo_data2.csv has been added to the target database:

    Management console
    CLI
    1. In the management console, select the folder with the DB you need.
    2. From the list of services, select Managed Service for YDB.
    3. Select the database from the list.
    4. Navigate to the Navigation tab.
    5. Make sure table1 now contains the new data.
    1. Connect to the Managed Service for YDB database.

    2. Run this request:

          SELECT * FROM table1;
      
      Response example
      Id |   Name   |   __file_name    | __row_index 
      ---+----------+------------------+-------------
       1 | "Anna"   | "demo_data1.csv" | 1 
       2 | "Robert" | "demo_data1.csv" | 2 
       3 | "Umar"   | "demo_data1.csv" | 3 
       4 | "Algul"  | "demo_data1.csv" | 4 
       5 | "Viktor" | "demo_data1.csv" | 5 
       6 | "Maria"  | "demo_data2.csv" | 1 
       7 | "Alex"   | "demo_data2.csv" | 2 
      

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:

  • Transfer

  • Source endpoint

  • Objects from the bucket

  • Delete the other resources depending on how they were created:

    Manually
    Using Terraform
    • Target endpoint.
    • Managed Service for YDB database.
    • Object Storage bucket.
    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
Object Storage in ClickHouse®
Next
YDB to ClickHouse®
© 2025 Direct Cursus Technology L.L.C.