Migrating data from Yandex Object Storage to Yandex Managed Service for PostgreSQL using Yandex Data Transfer
Note
You can migrate data from Yandex Object Storage to the Managed Service for PostgreSQL table using Data Transfer. To do this:
If you no longer need the resources you created, delete them.
Required paid resources
The support cost for this solution includes:
- Fee for an Object Storage bucket: data storage and data operations (see Object Storage pricing).
- Managed Service for PostgreSQL cluster fee: use of computing resources allocated to hosts and disk space (see Managed Service for PostgreSQL pricing).
- Fee for public IP address assignment on cluster hosts (see Virtual Private Cloud pricing).
- Per-transfer fee: use of computing resources and number of transferred data rows (see Data Transfer pricing).
Getting started
Set up the infrastructure:
-
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>
-
If using security groups, make sure they are configured correctly and allow inbound connections to your cluster.
-
Create a service account named
storage-viewerwith thestorage.viewerrole. The transfer will use it to access the bucket. -
Create a static access key for the
storage-viewerservice account.
-
If you do not have Terraform yet, install it.
-
Get the authentication credentials. You can add them to environment variables or specify them later in the provider configuration file.
-
Configure and initialize a provider. There is no need to create a provider configuration file manually, you can download it
. -
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.
-
Download the objstorage-to-postgres.tf
configuration file to the same 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.
-
In the
objstorage-to-postgres.tffile, specify the following: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.
-
Make sure the Terraform configuration files are correct using this command:
terraform validateTerraform will display any configuration errors detected in your files.
-
Create the required infrastructure:
-
Run this command to view the planned changes:
terraform planIf 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.
-
If everything looks correct, apply the changes:
-
Run this command:
terraform apply -
Confirm updating the resources.
-
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 data
-
Create
demo_data.csvon the running instance and fill it with test data:1,Anna 2,Robert 3,Umar 4,Algul 5,Viktor -
Upload the file you prepared to the Object Storage bucket.
Set up your transfer
-
Create a source endpoint of the
Object Storagetype with these 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 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 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
Manualand specify field names and data types:Id:Int64Name:UTF8
Keep the default values for all other settings.
-
-
Create a target endpoint and set up the transfer:
ManuallyTerraform-
Create a target endpoint of the
PostgreSQLtype 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>.
- Installation type:
-
Create a transfer of the Snapshot type that will use the new endpoints.
-
In the
objstorage-to-postgres.tffile, specify the following variables:source_endpoint_id: ID of the source endpoint.transfer_enabled: Set to1to create a transfer.
-
Make sure the Terraform configuration files are correct using this command:
terraform validateTerraform will display any configuration errors detected in your files.
-
Create the required infrastructure:
-
Run this command to view the planned changes:
terraform planIf 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.
-
If everything looks correct, apply the changes:
-
Run this command:
terraform apply -
Confirm updating the resources.
-
Wait for the operation to complete.
-
-
-
Activate the transfer
-
Activate the transfer and wait until its status switches to Completed.
-
Connect to the Managed Service for PostgreSQL target cluster database.
-
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 created
Some resources are not free of charge. To avoid paying for them, delete the resources you no longer need:
-
Bucket objects.
-
Delete other resources using the same method used for their creation:
ManuallyTerraform-
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.
-
Delete resources:
-
Run this command:
terraform destroy -
Confirm deleting the resources and wait for the operation to complete.
All the resources described in the Terraform manifests will be deleted.
-
-