Migrating data from Yandex Managed Service for OpenSearch to Yandex Managed Service for YDB using Yandex Data Transfer

With Data Transfer, you can transfer data from a Managed Service for OpenSearch cluster to a Managed Service for YDB DB.

To transfer data:

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

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

Required paid resourcesRequired paid resources

• Managed Service for OpenSearch cluster: Use of computing resources and storage size (see Managed Service for OpenSearch pricing).

• Public IP addresses if public access is enabled for cluster hosts (see Virtual Private Cloud pricing).

• Managed Service for YDB database (see Managed Service for YDB pricing). Its pricing is based on deployment mode:

  • In serverless mode, you pay for data operations and storage volume, including stored backups.
  • In dedicated instance mode, you pay for the use of computing resources allocated to the database, storage size, and backups.

Getting startedGetting started

Set up the infrastructure:

Prepare your test dataPrepare your test data

1. Connect to the source Managed Service for OpenSearch cluster.

2. Create a test index named people and set its schema:

   curl --user admin:<password> \
        --cacert ~/.opensearch/root.crt \
        --header 'Content-Type: application/json' \
        --request PUT 'https://<address_of_OpenSearch_host_with_DATA_role>:9200/people' && \
   curl --user admin:<password> \
        --cacert ~/.opensearch/root.crt \
        --header 'Content-Type: application/json' \
        --request PUT 'https://<address_of_OpenSearch_host_with_DATA_role>:9200/people/_mapping?pretty' \
        --data'
        {
              "properties": {
                 "name": {"type": "text"},
                 "age": {"type": "integer"}
              }
        }
        '
   

3. Populate the test index with data:

   curl --user admin:<password> \
        --cacert ~/.opensearch/root.crt \
        --header 'Content-Type: application/json' \
        --request POST 'https://<address_of_OpenSearch_host_with_DATA_role>:9200/people/_doc/?pretty' \
        --data'
        {
              "name" : "Alice",
              "age" : "30"
        }
        ' && \
   curl --user admin:<password> \
        --cacert ~/.opensearch/root.crt \
        --header 'Content-Type: application/json' \
        --request POST 'https://<address_of_OpenSearch_host_with_DATA_role>:9200/people/_doc/?pretty' \
        --data'
        {
              "name" : "Robert",
              "age" : "32"
        }
        '
   

4. Optionally, check the data in the test index:

   curl --user admin:<password> \
        --cacert ~/.opensearch/root.crt \
        --header 'Content-Type: application/json' \
        --request GET 'https://<address_of_OpenSearch_host_with_DATA_role>:9200/people/_search?pretty'
   

Set up and activate the transferSet up and activate the transfer

1. Create an OpenSearch-type source endpoint with the following settings:

   • Connection type: Managed Service for OpenSearch cluster.
   • Managed Service for OpenSearch cluster: Select the Managed Service for OpenSearch cluster from the list.
   • User: admin.
   • Password: <user_password>.

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

   Manually

   Using Terraform

   1. Create a YDB target endpoint with the following settings:

      • Database: Select your ydb1 database from the list.

      • Service account ID: Select the ydb-account service account from the list.

   2. Create a Snapshot-type transfer configured to use the new endpoints.

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

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

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

   4. The transfer will activate automatically upon creation. Wait for its status to change to Completed.

Test the transferTest the transfer

1. Connect to the Managed Service for YDB database.

2. Run this query:

   SELECT * FROM people;
   

   Response example

   # |          _id           | age | name
   --+------------------------+-----+---------
   0 | "5wn5BJEBRVOYnL8d13sP" | 30  | "Alice"
   1 | "6An5BJEBRVOYnL8d13uy" | 32  | "Robert"
   

Delete the resources you createdDelete the resources you created

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

1. Delete the resources depending on how you created them:

   Manually

   Using Terraform

   1. Delete the transfer.

   2. Delete the target endpoint.

   3. Delete the Managed Service for OpenSearch cluster.

   4. Delete the Managed Service for YDB database.

   5. Delete the service account.

   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.

2. Delete the source endpoint.