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 Managed Service for PostgreSQL
  • Getting started
    • All tutorials
    • Creating a PostgreSQL cluster for 1C
    • Creating a cluster of 1C:Enterprise Linux servers with a Managed Service for PostgreSQL cluster
    • Exporting a database to Yandex Data Processing
    • Searching for cluster performance issues
    • Performance analysis and tuning
    • Setting up a connection from a container in Serverless Containers
    • Delivering data to Yandex Managed Service for Apache Kafka® using Yandex Data Transfer
    • Delivering data to Yandex Managed Service for YDB using Yandex Data Transfer
    • Delivering data to Yandex Managed Service for Apache Kafka® using Debezium
    • PostgreSQL change data capture and delivery to YDS
    • Delivering data from Yandex Managed Service for Apache Kafka® using Yandex Data Transfer
    • Transferring data from Yandex Object Storage using Yandex Data Transfer
    • Configuring a fault-tolerant architecture in Yandex Cloud
    • Monitoring the status of geographically distributed devices
    • Writing load balancer logs to PostgreSQL
    • Creating an MLFlow server for logging experiments and artifacts
    • Working with data using Query
    • Federated data queries using Query
    • Fixing string sorting issues after upgrading glibc
    • Writing data from a device to a database
  • Access management
  • Pricing policy
  • Terraform reference
  • Monitoring metrics
  • Audit Trails events
  • Public materials
  • Release notes

In this article:

  • Required paid resources
  • Getting started
  • Prepare your test data
  • Set up the transfer
  • Activate the transfer
  • Delete the resources you created
  1. Tutorials
  2. Transferring data from Yandex Object Storage using Yandex Data Transfer

Transferring data from Yandex Object Storage using Yandex Data Transfer

Written by
Yandex Cloud
Updated at January 27, 2026
  • Required paid resources
  • Getting started
  • Prepare your test data
  • Set up the transfer
  • Activate the transfer
  • Delete the resources you created

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

  1. Prepare your test data.
  2. Set up the transfer.
  3. Activate the transfer.

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

Required paid resourcesRequired paid resources

  • Object Storage bucket: Use of storage, data operations (see Object Storage pricing).
  • Managed Service for PostgreSQL cluster: Computing resources allocated to hosts, storage and backup size (see Managed Service for PostgreSQL pricing).
  • Public IP addresses if public access is enabled for cluster hosts (see Virtual Private Cloud pricing).

Getting startedGetting started

Set up your infrastructure:

Manually
Terraform
  1. [Create a Managed Service for PostgreSQL] target cluster(../../managed-postgresql/operations/cluster-create.md) using any suitable base configuration and the following settings:

    • Public access to cluster hosts: Allowed.
    • DB name: db1.
    • Username: pg-user.
    • Password: <user_password>.
  2. If using security groups, make sure they are configured correctly and allow connections to your cluster.

  3. Create a Yandex Object Storage bucket.

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

  5. Create a static access key for the storage-viewer service 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 objstorage-to-postgres.tf configuration file to your current working directory.

    This file describes:

    • Network.
    • Subnet.
    • Cluster access security group.
    • Service account for bucket operations, e.g., creation and access.
    • Yandex Lockbox secret for the service account static key required to configure the source endpoint.
    • Object Storage source bucket.
    • Target Managed Service for PostgreSQL cluster.
    • Target endpoint.
    • Transfer.
  6. In the objstorage-to-postgres.tf file, specify the following:

    • folder_id: Cloud folder ID matching the one specified in your provider settings.
    • bucket_name: Bucket name consistent with the naming conventions.
    • pg_password: PostgreSQL user password.
  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 your test dataPrepare your test data

  1. On your local machine, create the demo_data.csv file and fill it with test data:

    1,Anna
    2,Robert
    3,Umar
    4,Algul
    5,Viktor
    
  2. Upload your prepared file to the Object Storage bucket.

Set up the transferSet up the transfer

  1. Create a source endpoint of the Object Storage type with the following settings:

    • Database type: Object Storage.

    • Bucket: Object Storage bucket name.

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

    • Secret Access Key: Service account’s secret access key. If you created your infrastructure using Terraform, copy the key’s value from the Yandex Lockbox secret.

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

    • Region: ru-central1.

    • Data format: CSV.

    • Delimiter: Comma (,).

    • Table: Name of the CSV file in the bucket, e.g., demo_data.csv.

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

      • Id: Int64
      • Name: UTF8

    Keep the default values for all other settings.

  2. Create a target endpoint and set up the transfer:

    Manually
    Terraform
    1. Create a PostgreSQL-type target endpoint and specify its cluster connection settings:

      • Installation type: Managed Service for PostgreSQL cluster.
      • Managed Service for PostgreSQL cluster: Select the name of the PostgreSQL source cluster from the drop-down list.
      • Database: db1.
      • User: pg-user.
      • Password — <user_password>.
    2. Create a transfer of the Snapshot-type that will use the endpoints you created.

    1. In the objstorage-to-postgres.tf file, specify the following variables:

      • source_endpoint_id: Source endpoint ID.
      • transfer_enabled: Set to 1 to create a 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.

Activate the transferActivate the transfer

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

  2. Connect to the database in the target Managed Service for PostgreSQL cluster.

  3. Run this request:

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

Data successfully migrated.

Delete the resources you createdDelete the resources you created

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

  1. Delete the transfer.

  2. Delete the source endpoint.

  3. Delete the objects from the bucket.

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

    Manually
    Terraform
    1. Delete the target endpoint.
    2. Delete the Managed Service for PostgreSQL cluster.
    3. Delete the 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
Delivering data from Yandex Managed Service for Apache Kafka® using Yandex Data Transfer
Next
Configuring a fault-tolerant architecture in Yandex Cloud
© 2026 Direct Cursus Technology L.L.C.