Complete Guide - Migration Assistant tool for AWS OpenSearch
This guide provides a comprehensive walkthrough for using the Migration Assistant tool to migrate from Elasticsearch to AWS OpenSearch Service. Follow each step carefully and ensure all prerequisites are met before beginning the migration process.
Overview
Migration Assistant addresses key limitations in traditional migration approaches. For example, if you're upgrading across multiple major versions—such as from Elasticsearch 6.8 to OpenSearch 2.19—you can use Migration Assistant to complete the process in a single step. Other methods, like rolling upgrades or snapshot restoration, require upgrading through each major version and often reindexing at every stage.
Supported platforms
Source and target platforms
- Self-managed (on premises or hosted by a cloud provider)
- Amazon OpenSearch Service (Amazon OpenSearch Serverless collections are not supported)
- Refer to Supported AWS Regions for the full list of supported Regions.
Before starting an upgrade or migration, consider the cluster feature to be included. The following table lists what can be migrated using Migration Assistant, whether it is currently supported, and recommendations for how to handle each component.
| Feature | Supported | Recommendations |
|---|---|---|
| Documents | Yes | Migrate existing data with RFS and live traffic with Capture and Replay. |
| Index settings | Yes | Migrate with the Metadata-Migration-Tool. |
| Index mappings | Yes | Migrate with the Metadata-Migration-Tool. |
| Index templates | Yes | Migrate with the Metadata-Migration-Tool. |
| Component templates | Yes | Migrate with the Metadata-Migration-Tool. |
| Aliases | Yes | Migrate with the Metadata-Migration-Tool. |
Architecture
Deploying this solution with the default parameters deploys the following components in your AWS account.
Each node in the diagram correlates to the following steps in the migration process:
- Client traffic is directed to the existing cluster.
- An Application Load Balancer with capture proxies relays traffic to a source while replicating data to Amazon Managed Streaming for Apache Kafka (Amazon MSK).
- Using the migration console, a point-in-time snapshot is taken. Once the snapshot completes, the Metadata Migration Tool is used to establish indexes, templates, component templates, and aliases on the target cluster. With continuous traffic capture in place, Reindex-from-Snapshot migrates data from the source.
- Once Reindex-from-Snapshot is complete, captured traffic is replayed from Amazon MSK to the target cluster by Traffic Replayer.
- Performance and behavior of traffic sent to the source and target clusters are compared by reviewing logs and metrics.
- After confirming that the target cluster's functionality meets expectations, clients are redirected to the new target.
Migration Assistant assumptions and limitations
Before using Migration Assistant, review the following assumptions and limitations.
1. Networking and environment
Connectivity to AWS services and outbound internet access are required in order to build and deploy Migration Assistant. Requirements differ based on whether you're deploying to a new or existing virtual private cloud (VPC).
2. Source and target connectivity
To meet connectivity requirements, ensure the following:
-
You must establish connectivity between:
- The source cluster and Migration Assistant.
- The target cluster and Migration Assistant.
- S3 bucket for snapshot and Migration Assistant.
-
If the source or target resides in a private VPC without internet access, use one of the following to connect:
- VPC endpoints
- VPC peering
- AWS Transit Gateway
3. Deploying to a new VPC
When deploying to a new VPC, consider the following:
- Migration Assistant provisions a new VPC with required components (for example, NAT gateway, subnets).
- You must establish network access from this VPC to both the source and target clusters.
4. Deploying to an existing VPC
When deploying to an existing VPC, consider the following:
- If deploying Migration Assistant to an existing VPC (for example, the same VPC as the source or target), you may need to configure connectivity to any cluster external to the target VPC.
- For example, if Migration Assistant is deployed to the source VPC, you may need VPC endpoints or peering to reach the target.
- Ensure all required AWS services are reachable by Migration Assistant components.
- If the VPC has outbound access using private subnets with a NAT gateway or public subnets with an internet gateway, then VPC endpoints are not required.
- If using isolated subnets with no outbound access, you must configure VPC endpoints or routing to the following services:
- Amazon VPC – Ensures proper routing, DNS resolution, and endpoint configuration.
- Amazon CloudWatch – Publishes migration metrics.
- Amazon CloudWatch Logs – Ingests Amazon Elastic Container Service (Amazon ECS) task logs.
- Amazon Elastic Compute Cloud (Amazon EC2) – Used to bootstrap Migration Assistant. When deploying using AWS CloudFormation, the bootstrap EC2 instance requires outbound internet access (using NAT gateway or an internet gateway) to download the latest version from GitHub.
- Amazon Elastic Container Registry (Amazon ECR) – Pulls container images.
- Amazon ECS – Orchestrates container workloads.
- Amazon Elastic File System (Amazon EFS) – Stores persistent logs.
- Amazon Managed Streaming for Apache Kafka (Amazon MSK) (Capture and Replay only) – Used as durable storage to capture and replay live HTTP traffic.
- Amazon S3 – Stores and retrieves snapshots and artifacts.
- Elastic Load Balancing (Capture and Replay only) – Used by the migration console to connect to the Application Load Balancer.
- AWS Secrets Manager – Securely stores credentials when using basic authentication on the source or target.
- AWS Systems Manager
- AWS X-Ray – Supports distributed tracing.
5. Reindex-from-Snapshot
To use Reindex-from-Snapshot (RFS), ensure the following:
- The _source field must be enabled on all indexes to be migrated.
- The source cluster must have the Amazon S3 plugin installed.
- If you choose to bring your own snapshot (that is, one not created by Migration Assistant), the following settings must be applied when creating the snapshot:
- include_global_state: true – Ensures that global cluster state is included.
- compress: false – Disables metadata compression, which is required for compatibility with RFS.
- Shards of up to 80 GiB are supported by default. Larger shard sizes can be configured, except in AWS GovCloud (US), where 80 GiB is the maximum.
- In OpenSearch 2.9 and later, snapshots of indexes that use the zstd or zstd_no_dict codecs are not supported. If you need to migrate these indexes using Reindex-from-Snapshot, you must first reindex them on the source cluster using either default or best_compression before creating a new snapshot for use with RFS.
6. Capture and Replay
Capture and Replay has the following requirements:
- The Traffic Capture Proxy must be deployed to intercept client traffic.
- Live capture is recommended only for workloads with < 4 TB/day of incoming traffic to the source cluster.
- Automatically generated document IDs are not preserved during replay. Clients must explicitly provide document IDs for index and update operations.
- Migration Assistant does not guarantee zero-downtime migration through live traffic Capture and Replay for migration paths starting from Elasticsearch 1.x and Elasticsearch 2.x.
Key components
The following are the key components of Migration Assistant.
1. Elasticsearch/OpenSearch source
In this solution, your source cluster operates on either Elasticsearch or OpenSearch and is hosted on Amazon EC2 instances or in a similar computing environment. The source cluster may also be managed by AWS, an alternative cloud provider, or hosted on premises. Traffic is rerouted from the source cluster to a Traffic Capture Proxy and replayed to a target, typically on a later version of OpenSearch.
2. Migration console
The migration console provides a migration-specific CLI and offers a variety of tools for streamlining the migration process. You can perform everything necessary for completing a migration, other than cleaning up the migration resources and managing application changes, through this console.
3. Traffic Capture Proxy
This component is designed for HTTP RESTful traffic. It forwards traffic to the source cluster and also splits and channels this traffic to a stream processing service for later playback.
4. Traffic Replayer
Acting as a traffic simulation tool, Traffic Replayer replays recorded request traffic to a target cluster, mirroring source traffic patterns. It links original requests and their responses to those directed at the target cluster, facilitating comparative analysis.
5. Metadata Migration Tool
The metadata migration tool integrated into the Migration CLI can be used independently to migrate cluster metadata, including index mappings, index configuration settings, templates, component templates, and aliases.
6. Reindex-from-Snapshot
Reindex-from-Snapshot (RFS) reindexes data from an existing snapshot. Amazon ECS workers coordinate the migration of documents from an existing snapshot, reindexing the documents in parallel to a target cluster.
7. Target cluster
The target cluster is the destination cluster for an upgrade or migration. It may also be a cluster on the same version that has been reconfigured to meet changing application needs.
Assessment
- The goal of Migration Assistant is to streamline the process of migrating from one location or version of Elasticsearch/OpenSearch to another. However, completing a migration sometimes requires resolving client compatibility issues before they can communicate directly with the target cluster.
- Before performing any upgrade or migration, you should review any breaking changes that might exist between versions because there may be changes required in order for clients to connect to the new cluster.
- Use the following link by selecting the versions in your migration path: OpenSearch Migration Assessment
Deploy
- This quickstart assumes that you have performed an assessment as mentioned above to understand upgrade breaking changes and limitations before beginning.
- This quickstart outlines how to deploy Migration Assistant for OpenSearch and execute an existing data migration using RFS.
- This solution uses AWS CloudFormation templates and stacks to automate its deployment. The CloudFormation template specifies the AWS resources included in this solution and their properties. The CloudFormation stack provisions the resources that are described in the template.
1. Download the CloudFormation template
- Launch in a new VPC: CloudFormation Template
- Launch in an existing VPC: CloudFormation Template
2. Launch the bootstrap stack
- First download the CloudFormation template according to your use case - either launch in new VPC or launch in an existing VPC.
- The template launches in the US East (N. Virginia) Region by default. To launch the solution in a different AWS Region, use the Region selector in the console navigation bar. For replication purpose I'm choosing Frankfurt eu-central-1 region.
- On the Create stack page, verify that the correct template URL (If it's for a new VPC, the name is migration-assistant-for-amazon-opensearch-service-create-vpc.template. If it's for an existing VPC, the name is migration-assistant-for-amazon-opensearch-service-import-vpc.template) is in the Amazon S3 URL text box and choose Next.
- Give the stack name and stage name.
- On the Review and create page, review and confirm the settings. Select the box acknowledging that the template might create IAM resources.
- Choose Submit to deploy the stack.
- In the AWS CloudFormation stack page you will see the stack in
CREATE_IN_PROGRESS. Please wait for 5-10 minutes for stack to get deployed.
3. Set up Bootstrap instance access
- Once the stack is deployed and status is
CREATE_COMPLETE, navigate to AWS EC2 service page where you will see a running instance by the name -bootstrap-instance-stage-region - Create an IAM policy using the following snippet, replacing
<aws-region>,<aws-account>,<stage>, and<ec2-instance-id>with your information:
{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Action": "ssm:StartSession",
"Resource": [
"arn:aws:ec2:<aws-region>:<aws-account>:instance/<ec2-instance-id>",
"arn:aws:ssm:<aws-region>:<aws-account>:document/BootstrapShellDoc-<stage>-<aws-region>"
]
}
]
}
- Name the policy, for example,
SSM-OSMigrationBootstrapAccess, and then create the policy by selecting Create policy. - Attach the newly created policy to your EC2 instance's IAM role.
- SSH into the instance. For this replication I'm using session-manager option to login from AWS EC2 console.
- Once logged in, run the following command from the shell of the Bootstrap instance:
sudo -s
cd /opensearch-migrations directory
./initBootstrap.sh && cd deployment/cdk/opensearch-service-migration
- After a successful build, it will give you output as:
BUILD SUCCESSFUL in 24m
153 actionable tasks: 131 executed, 22 from cache
Configuration cache entry stored.
4. Customize the migration options
- Now run
lscommand and you will seecdk.context.jsonfile and when you runvi cdk.context.jsoncommand you will have below content. For replication purpose I'm using non FGAC clusters and mentioning auth type as sigv4:
{ "default": { "stage": "stage", "targetCluster": { "endpoint": "https://vpc-os-2-19-v-------xmqvur6a.region.es.amazonaws.com", "// allow_insecure documentation": "Set this to true to ignore when the target cluster's HTTP certificate was not signed with a trusted CA Root Certificate. Default: true", "allow_insecure": true, "auth": { "type": "sigv4", "region": "region", "serviceSigningName": "es" } }, "sourceCluster": { "endpoint": "https://vpc-es-5-6-j-------xduy.region.es.amazonaws.com", "// allow_insecure documentation": "Set this to true to ignore when the source cluster's HTTP certificate was not signed with a trusted CA Root Certificate. Default: true", "allow_insecure": true, "version": "ES_5.6", "auth": { "type": "sigv4", "region": "region", "serviceSigningName": "es" } }, "MskEbsStorage":{ "maxCapacity": 16384 }, "vpcId": "vpc-06f------f15c", "// help vpcAZCount": "For deployments using the capture-proxy, this AZ count should match the source cluster AZ count.", "vpcAZCount": 2, "reindexFromSnapshotServiceEnabled": true, "reindexFromSnapshotMaxShardSizeGiB": 80, "// settingsForCaptureAndReplay": "Enable the following services for live traffic capture and replay:", "trafficReplayerServiceEnabled": true, "captureProxyServiceEnabled": true, "targetClusterProxyServiceEnabled": false, "// help capture/target proxy pt. 1 of 2": "captureProxyService and targetClusterProxyService deployment will fail without network access to clusters.", "// help capture/target proxy pt. 2 of 2": "In most cases, keep the desired count setting at 0 until you verify connectivity in the migration console. After verifying connectivity, you can redeploy with a higher desired count.", "captureProxyDesiredCount": 0, "targetClusterProxyDesiredCount": 0, "// help trafficReplayerExtraArgs": "Increase the speedup factor to replay requests at a faster rate in order to catch up.", "trafficReplayerExtraArgs": "--speedup-factor 1.5" } }
- Save the file and exit of edit.
5. Bootstraping your account
- After the cdk.context.json file is fully configured, bootstrap the account and deploy the required stacks using the following command:
export AWS_DEFAULT_REGION=<region>
cdk bootstrap --c contextId=default
- Once you successfully bootstrap your account, you will a CloudFormation stack named
CDKToolkitin your AWS account and on command line of EC2 instance you will see below output:
CDKToolkit: creating CloudFormation changeset...
✅ Environment aws://<account-id>/<region> bootstrapped.
6. Deploy Migration Assistant
- This step will take approx 30 minutes to complete.
- Deploy Migration Assistant using the following command:
cdk deploy "*" --c contextId=default --require-approval never --concurrency 5
7. Verify the Migration Assistant
- From the same Bootstrap instance shell, verify that all CloudFormation stacks were installed successfully:
aws cloudformation list-stacks --query "StackSummaries[?StackStatus!='DELETE_COMPLETE'].[StackName,StackStatus]" --output table
- You should receive a similar output for your Region.
-----------------------------------------------------------------------------------------------
| ListStacks |
+--------------------------------------------------------------------------+------------------+
| OSMigrations-stage-region-MigrationConsole | CREATE_COMPLETE |
| OSMigrations-stage-region-CaptureProxy | CREATE_COMPLETE |
| OSMigrations-stage-region-default-TrafficReplayer | CREATE_COMPLETE |
| OSMigrations-stage-region-ReindexFromSnapshot | CREATE_COMPLETE |
| OSMigrations-stage-region-MigrationInfra | CREATE_COMPLETE |
| OSMigrations-stage-region-default-NetworkInfra | CREATE_COMPLETE |
| CDKToolkit | CREATE_COMPLETE |
| Migration-OS-1 | CREATE_COMPLETE |
+--------------------------------------------------------------------------+------------------+
8. (Optional) RFS parameters
- If you're creating a snapshot using migration tooling, these parameters are automatically configured. If you're using an existing snapshot, modify the reindexFromSnapshotExtraArgs setting with the following values:
"reindexFromSnapshotExtraArgs": "--s3-repo-uri s3://<bucket-name>/<repo> --s3-region <region> --snapshot-name <name>"
- You will also need to give the migration console and RFS TaskRoles permissions to the S3 bucket.
9. Access the migration console
- Run the following command to access the migration console:
cd /opensearch-migrations/deployment/cdk/opensearch-service-migration/
./accessContainer.sh migration-console <stage> <region>
- You will see below migration-console when you access the migration console:
[root@ip-1x-2xx-----xx opensearch-service-migration]# ./accessContainer.sh migration-console <stage> <region>
The Session Manager plugin was installed successfully. Use the AWS CLI to start a session.
Starting session with SessionId: ecs-execute-command-djzep4------xxcy2dca
Welcome to the Migration Assistant Console
(14:15:19) migration-console (~) ->
10. Verify the connection to the source and target clusters
- To verify the connection to the clusters, run the following command:
(14:15:19) migration-console (~) -> console clusters connection-check
- You should receive the following output:
SOURCE CLUSTER
ConnectionResult(connection_message='Successfully connected!', connection_established=True, cluster_version='5.6.17')
TARGET CLUSTER
ConnectionResult(connection_message='Successfully connected!', connection_established=True, cluster_version='2.19.0')
Congratulations! Now you have logged into migration-console and checked the connection between 2 clusters which is created successfully.
- You can list the indices present in your source and target cluster using below command:
(14:15:19) migration-console (~) -> console clusters cat-indices
Output:
WARNING: Cluster information may be stale. Use --refresh to update.
SOURCE CLUSTER
health status index uuid pri rep docs.count docs.deleted store.size pri.store.size
green open .kibana l7xoe5e-------x96Yqg 1 1 1 0 6.4kb 3.2kb
green open my-new-index-1 vm1jtX4-------xfOrPg 1 1 2 0 18.2kb 9.1kb
TARGET CLUSTER
health status index uuid pri rep docs.count docs.deleted store.size pri.store.size
green open .plugins-ml-config dt15Ntih-------xS9sQ 1 1 1 0 7.8kb 3.9kb
green open .opensearch-observability qdGN99Qu-------xoU9w 1 1 0 0 416b 208b
green open .kibana_1 ITlWUQOR-------xp9OQ 1 1 1 0 10.4kb 5.2kb
Creating a snapshot
- Creating a snapshot of the source cluster captures all the metadata and documents to be migrated to a new target cluster.
- Run the following command to initiate snapshot creation from the source cluster:
(14:15:19) migration-console (~) -> console snapshot create
Output:
2025-10-31 14:25:18,295 INFO o.o.m.u.ProcessHelpers [main] getNodeInstanceName()=ip-1x---------xx.<region>.compute.internal_ecc7720------x50b78f03
2025-10-31 14:25:19,779 INFO o.o.m.b.w.SnapshotRunner [main] Attempting to initiate the snapshot...
2025-10-31 14:25:19,780 INFO o.o.m.b.c.OpenSearchClient [main] Starting registerSnapshotRepo for repoName=migration_assistant_repo
2025-10-31 14:25:20,408 INFO o.o.m.b.c.OpenSearchClient [main] Completed registerSnapshotRepo for repoName=migration_assistant_repo in 628 ms with statusCode=200
2025-10-31 14:25:20,409 INFO o.o.m.b.c.SnapshotCreator [main] Snapshot repo registration successful
2025-10-31 14:25:20,409 INFO o.o.m.b.c.OpenSearchClient [main] Starting createSnapshot for repoName=migration_assistant_repo, snapshotName=rfs-snapshot
2025-10-31 14:25:20,668 INFO o.o.m.b.c.OpenSearchClient [main] Completed createSnapshot for repoName=migration_assistant_repo, snapshotName=rfs-snapshot in 259 ms with statusCode=200
2025-10-31 14:25:20,669 INFO o.o.m.b.c.SnapshotCreator [main] Snapshot rfs-snapshot creation initiated
2025-10-31 14:25:20,669 INFO o.o.m.b.w.SnapshotRunner [main] Snapshot in progress...
Starting program with: --snapshot-name rfs-snapshot --snapshot-repo-name migration_assistant_repo --source-host https://vpc-es-5-6-j-------xduy.<region>.es.amazonaws.com:443 --source-aws-service-signing-name es --source-aws-region <region> --source-insecure --otel-collector-endpoint http://localhost:4317 --s3-repo-uri s3://migration-artifacts-<account-id>-<stage>-<region>/rfs-snapshot-repo --s3-region <region> --no-wait --s3-role-arn arn:aws:iam::<account-id>:role/OSMigrations-<stage>-<region>-default-SnapshotRole
Snapshot rfs-snapshot creation initiated successfully
- Migration Assistant will automatically generate a snapshot name and configure the necessary Amazon Simple Storage Service (Amazon S3) repository. Alternatively, you have the option to bring your own existing snapshot.
- To check the snapshot creation status, run the following command:
(14:15:19) migration-console (~) -> console snapshot status
- To retrieve more information about the snapshot, run the following command:
(14:15:19) migration-console (~) -> console snapshot status --deep-check
- Wait for snapshot creation to complete before proceeding to the metadata migration phase.
- You should receive the following response when you run above
--deep-checkcommand :
Snapshot status: SUCCESS
Start time: 2025-10-31 14:25:20
Finished time: 2025-10-31 14:25:21
Percent completed: 100.00%
Estimated time to completion: 0h 0m 0s
Data processed: 0.000/0.000 MiB
Throughput: 0.000 MiB/sec
Total shards: 2
Successful shards: 2
Migrate your data using RFS
- Metadata migration involves creating a snapshot of your cluster and then migrating the metadata from the snapshot using the migration console.
- This tool gathers information from a source cluster through a snapshot or through HTTP requests against the source cluster. These snapshots are fully compatible with the backfill process for RFS scenarios.
- After collecting information on the source cluster, comparisons are made against the target cluster. If running a migration, any metadata items that do not already exist will be created on the target cluster.
- For the following commands, to identify all valid arguments:
(14:15:19) migration-console (~) -> console metadata evaluate
Output:
Starting Metadata Evaluation
Clusters:
Source:
Type: Snapshot (ELASTICSEARCH 5.6.0)
S3 repository: s3://migration-artifacts-<account-id>-<stage>-<region>/rfs-snapshot-repo
Target:
Type: Remote Cluster (AMAZON_MANAGED_OPENSEARCH 2.19.0)
Uri: https://vpc-os-2-19-v-------xmqvur6a.<region>.es.amazonaws.com:443
Protocol: HTTPS
TLS Verification: Disabled
AWS Auth: Enabled
Migration Candidates:
Index Templates:
<NONE FOUND>
Component Templates:
<NONE FOUND>
Indexes:
- my-new-index-1
WARN - .kibana skipped due to filter
Aliases:
<NONE FOUND>
Transformations:
Field Data Type Deprecation - string:
Convert field data type string to text/keyword
Version Transform:
Other transforms for source to target shape conversion
Results:
0 issue(s) detected
- As you can see above output, my source cluster has
my-new-index-1which will be migrated to target cluster when we run migrate command. - Execute following command to perform the migration:
(14:15:19) migration-console (~) -> console -v metadata migrate
- You should receive a response similar to the following:
Starting Metadata Migration
Clusters:
Source:
Type: Snapshot (ELASTICSEARCH 5.6.0)
S3 repository: s3://migration-artifacts-<account-id>-<stage>-<region>/rfs-snapshot-repo
Target:
Type: Remote Cluster (AMAZON_MANAGED_OPENSEARCH 2.19.0)
Uri: https://vpc-os-2-19-v-------xmqvur6a.<region>.es.amazonaws.com:443
Protocol: HTTPS
TLS Verification: Disabled
AWS Auth: Enabled
Migrated Items:
Index Templates:
<NONE FOUND>
Component Templates:
<NONE FOUND>
Indexes:
- my-new-index-1
WARN - .kibana skipped due to filter
Aliases:
<NONE FOUND>
Transformations:
Field Data Type Deprecation - string:
Convert field data type string to text/keyword
Version Transform:
Other transforms for source to target shape conversion
Results:
0 issue(s) detected
Command executed successfully
- Once you receive above output, you can verify the migration via RFS using below command:
(14:15:19) migration-console (~) -> console clusters cat-indices
Output:
SOURCE CLUSTER
health status index uuid pri rep docs.count docs.deleted store.size pri.store.size
green open .kibana l7xoe5e-------x96Yqg 1 1 1 0 6.4kb 3.2kb
green open my-new-index-1 vm1jtX4-------xfOrPg 1 1 2 0 18.5kb 9.2kb
TARGET CLUSTER
health status index uuid pri rep docs.count docs.deleted store.size pri.store.size
green open .plugins-ml-config dt15Ntih-------xS9sQ 1 1 1 0 7.8kb 3.9kb
green open .opensearch-observability qdGN99Qu-------xoU9w 1 1 0 0 416b 208b
green open my-new-index-1 ITlWUQOR-------xp9OQ 1 1 2 0 18.5kb 9.2kb
green open .kibana_1 YXlWUQOR-------xp9OQ 1 1 1 0 10.4kb 5.2kb
- In this way I have successfully migrated data from source AWS Elasticsearch 5.6 cluster to AWS Opensearch 2.19 cluster.
Using backfill
After the metadata for your cluster has been migrated, you can use Capture Proxy data replication and snapshots to backfill your data into the next cluster.
1. Starting the backfill
- To start the migration from RFS, start a backfill using the following command:
(14:15:19) migration-console (~) -> console backfill start
- The status will be Running even if all the shards have been migrated.
Output:
Backfill started successfully.
Service migration-dev-reindex-from-snapshot set to 5 desired count. Currently 0 running and 0 pending.
2. Monitoring the backfill
- To check the status of the documentation backfill, use the following command:
(14:15:19) migration-console (~) -> console backfill status
Output:
BackfillStatus.RUNNING
Running=1 Pending=4 Desired=5 Terminating=0
- Use the following command to perform detailed monitoring of the backfill process:
(14:15:19) migration-console (~) -> console backfill status --deep-check
Output:
BackfillStatus.RUNNING
Running=1 Pending=4 Desired=5 Terminating=0
Backfill percentage_completed: 100.0
Backfill started: 2025-10-31 14:51:02+00:00
Backfill finished: 2025-10-31 14:51:03+00:00
Backfill shard_total: 1
Backfill shard_complete: 1
Backfill shard_in_progress: 0
Backfill shard_waiting: 0
3. Validating the backfill
- After the backfill is complete and the workers have stopped, examine the contents of your cluster:
(14:15:19) migration-console (~) -> console clusters cat-indices --refresh
Output:
SOURCE CLUSTER
health status index uuid pri rep docs.count docs.deleted store.size pri.store.size
green open my-new-index-1 -DqPQDr-------Ss34bQ 1 1 3 0 25.4kb 12.7kb
TARGET CLUSTER
health status index uuid pri rep docs.count docs.deleted store.size pri.store.size
green open .opensearch-observability 8HOCom-------WIOGRbQ 1 1 0 0 416b 208b
green open .plugins-ml-config 9tld-P-------yDhlyhQ 5 1 1 0 9.5kb 4.7kb
green open my-new-index-1 bGfGtY-------leR5NAQ 1 1 3 0 25.4kb 12.7kb
green open .migrations_working_state lopd47-------ZuJGZOg 1 1 2 0 18.6kb 6.4kb
green open .kibana_1
Conclusion
Thus in this way you can successfully implement migration from Elasticsearch cluster to AWS Opensearch cluster without following the traditional approach.
Technical Documentation References
- OpenSearch Migration Assistant Documentation
- AWS Migration Assistant for Amazon OpenSearch Service
- Migration Assistant Solution Overview
- Topics
- Analytics
- Language
- English
Very useful article!
replied 10 months ago
Relevant content
asked 3 years ago
AWS OFFICIALUpdated 2 months ago