View a markdown version of this page

Workflow-driven operating model - Migration Assistant for Amazon OpenSearch Service

Workflow-driven operating model

Migration Assistant 3.0 is built around three ideas:

  1. Declare the migration once in workflow configuration instead of stitching together long-lived infrastructure by hand.

  2. Let Amazon EKS run the work so migration tasks can be created, retried, scaled, and cleaned up as Kubernetes-managed workloads.

  3. Use the Workflow CLI for submission, approval, validation, and cutover so customers think in terms of workflow configuration and approval gates rather than individual infrastructure commands.

A typical migration follows this lifecycle:

  1. Assess compatibility, unsupported components, and downtime needs.

  2. Deploy Migration Assistant on Amazon EKS using the bootstrap script.

  3. Configure the workflow from the version-matched sample on the Migration Console.

  4. Run a pilot on a small index allowlist.

  5. Submit the real workflow and monitor it through workflow manage.

  6. Approve gated transitions only after validation.

  7. Cut over to the Amazon OpenSearch Service domain or Amazon OpenSearch Serverless collection.

  8. Remove infrastructure only after the rollback window has passed.