Question

A retail company runs a self-managed Elasticsearch cluster on EC2 that indexes product catalog data. They are migrating to Amazon OpenSearch Service. The catalog is updated continuously by an application that writes to a relational database, and downstream search queries must never return stale results for more than a few minutes during the migration. The migration team wants the lowest-risk cutover with the ability to roll back if the new domain underperforms. Which approach best meets these requirements?

Accepted Answer

Configure the application's indexing pipeline to dual-write to both the self-managed cluster and the OpenSearch domain, backfill historical data via snapshot restore, validate query parity, and cut clients over gradually while keeping the old cluster available for rollback.

Answer

Take a snapshot of the self-managed cluster to Amazon S3, restore it into the OpenSearch domain, then immediately repoint all clients to the new domain and delete the old cluster.

Answer

Use AWS DMS to replicate the Elasticsearch indices directly into the OpenSearch domain with change data capture enabled, then switch clients once replication lag reaches zero.

Answer

Export the indices to CSV, load them into Amazon S3, use AWS Glue to transform the data, and bulk-load into OpenSearch before repointing clients.