Migrating data from Elasticsearch to Yandex Managed Service for OpenSearch
You can set up data transfer from Elasticsearch to Managed Service for OpenSearch indexes using Data Transfer. To do this:
- Configure the source cluster.
- Prepare your test data.
- Configure the target cluster.
- Set up and activate the transfer.
- Test the transfer.
If you no longer need the resources you created, delete them.
Required paid resources
- Managed Service for OpenSearch cluster, which includes the 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).
Getting started
-
Create a Managed Service for OpenSearch target cluster:
ManuallyTerraformCreate a Managed Service for OpenSearch target cluster in any suitable configuration with publicly accessible hosts.
Note
Public access to cluster hosts is required if you plan to connect to the cluster via the internet. This connection option is simpler and is recommended for the purposes of this guide. You can connect to non-public hosts as well but only from Yandex Cloud virtual machines located in the same cloud network as the cluster.
-
If you do not have Terraform yet, install it and configure the Yandex Cloud provider.
-
Download the file with provider settings
. Place it in a separate working directory and specify the parameter values. -
Download the data-transfer-es-mos.tf
configuration file to your current working directory.This file describes:
- Network.
- Subnet.
- Security group and rules for connecting to a Managed Service for OpenSearch cluster.
- Managed Service for OpenSearch target cluster.
- Transfer.
-
In the
data-transfer-es-mos.tffile, specify the following variables:mos_version: OpenSearch version.mos_admin_password: Managed Service for OpenSearch admin password.transfer_enabled: Set to0to ensure no transfer is created until you create endpoints manually.
-
Run the
terraform initcommand in the directory with the configuration file. This command initializes the provider specified in the configuration files and enables you to use its resources and data sources. -
Validate your Terraform configuration files 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
. -
-
-
Install the following tools:
Configure the source cluster
You can deliver data from the Elasticsearch cluster as admin with the superuser role; however, however, a more secure strategy is to create dedicated users with limited privileges for each job. To do this, create a user to execute the transfer:
-
In the source cluster, create a role
with thecreate_indexandwriteprivileges for all indexes (*). -
In the source cluster, create a user to run the transfer and assign the user the role you created.
Prepare your test data
-
In the source cluster, create a test index named
peopleand define its schema:curl --user <username_in_source_cluster>:<user_password_in_source_cluster> \ --header 'Content-Type: application/json' \ --request PUT 'https://<address_of_Elasticsearch_host_with_Data_role>:9200/people' && \ curl --user <username_in_source_cluster>:<user_password_in_source_cluster> \ --header 'Content-Type: application/json' \ --request PUT 'https://<address_of_Elasticsearch_host_with_Data_role>:9200/people/_mapping?pretty' \ --data' { "properties": { "name": {"type": "text"}, "age": {"type": "integer"} } } ' -
Populate the test index with data:
curl --user <username_in_source_cluster>:<user_password_in_source_cluster> \ --header 'Content-Type: application/json' \ --request POST 'https://<address_of_Elasticsearch_host_with_Data_role>:9200/people/_doc/?pretty' \ --data' { "name" : "Alice", "age" : "30" } ' && \ curl --user <username_in_source_cluster>:<user_password_in_source_cluster> \ --header 'Content-Type: application/json' \ --request POST 'https://<address_of_Elasticsearch_host_with_Data_role>:9200/people/_doc/?pretty' \ --data' { "name" : "Robert", "age" : "32" } ' -
Optionally, check the data in the test index:
curl --user <username_in_target_cluster>:<user_password_in_target_cluster> \ --header 'Content-Type: application/json' \ --request GET 'https://<address_of_Elasticsearch_host_with_Data_role>:9200/people/_search?pretty'
Configure the target cluster
-
Get an SSL certificate to connect to the Managed Service for OpenSearch cluster.
-
Optionally, create a user to run the transfer.
You can deliver data to the Managed Service for OpenSearch cluster as
adminwith thesuperuserrole; however, a more secure strategy is to create dedicated users with limited privileges for each job.-
Create a role
with thecreate_indexandwriteprivileges for all indexes (*). -
Create a user and assign this role to them.
-
Set up and activate the transfer
-
Create an endpoint for the Elasticsearch source.
-
Create an endpoint for the OpenSearch target.
-
Create a transfer:
ManuallyTerraform- Create a transfer of the Snapshot-type that will use the endpoints you created.
- Activate the transfer and wait for its status to change to Completed.
-
In the
data-transfer-mes-mos.tffile, specify the following variables:source_endpoint_id: Source endpoint ID.target_endpoint_id: Target endpoint ID.transfer_enabled: Set to1to create a transfer.
-
Validate your Terraform configuration files 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 and wait for its status to change to Completed.
Test the transfer
Check that the Managed Service for OpenSearch cluster's people index contains the data you sent:
Run this command:
curl --user <username_in_target_cluster>:<user_password_in_target_cluster> \
--cacert ~/.opensearch/root.crt \
--header 'Content-Type: application/json' \
--request GET 'https://<address_of_OpenSearch_host_with_Data_Node_role>:9200/people/_search?pretty'
- Connect to the target cluster using OpenSearch Dashboards.
- Select the
Globaltenant. - Open the management panel by clicking
. - Under OpenSearch Dashboards, select Discover.
- In the CHANGE INDEX PATTERN field, select the
peopleindex.
Delete the resources you created
To reduce the consumption of resources, delete those you do not need:
-
Delete the other resources depending on how you created them:
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.
-
-