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
  • Set up your transfer
  • Activate the transfer
  • Delete the resources you created
  1. Tutorials
  2. Uploading data to data marts
  3. Object Storage to PostgreSQL

Loading data from Yandex Object Storage to Yandex Managed Service for PostgreSQL

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

Note

The functionality for loading data from Object Storage in Data Transfer is at the Preview stage. To get access, contact support or your account manager.

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

  1. Prepare the test data.
  2. Set up your transfer.
  3. Activate 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 PostgreSQL cluster fee: Using computing resources allocated to hosts and disk space (see Managed Service for PostgreSQL pricing).
  • Fee for using public IP addresses 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 the infrastructure:

Manually
Terraform
  1. Create a Managed Service for PostgreSQL target cluster of any suitable configuration with the following settings:

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

  3. Create an 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 the same working directory.

    This file describes:

    • Network.
    • Subnet.
    • Security group required to connect to the cluster.
    • Service account for creating and accessing the bucket.
    • Yandex Lockbox secret with the static key of the service account for configuring the source endpoint.
    • Object Storage source bucket.
    • Managed Service for PostgreSQL target cluster.
    • Target endpoint.
    • Transfer.
  6. Specify the following in the objstorage-to-postgres.tf file:

    • folder_id: Cloud folder ID, same as in the provider settings.
    • bucket_name: Bucket name consistent with the naming conventions.
    • pg_password: PostgreSQL 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 demo_data.csv on the running instance and fill it with test data:

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

Set up your transferSet up your transfer

  1. Create a source endpoint of the Object Storage type with these 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: 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

    For the other properties, leave the default values.

  2. Create a target endpoint and transfer:

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

      • Installation type: Managed Service for PostgreSQL cluster.
      • Managed Service for PostgreSQL cluster: 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 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:

      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 until its status switches to Completed.

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

  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

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
    Terraform
    • Target endpoint.
    • Managed Service for PostgreSQL.
    • 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 MySQL®
Next
Object Storage to Greenplum®
© 2025 Direct Cursus Technology L.L.C.