Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Integrated Migration Suite for Amazon OpenSearch Service #1097

Open
sumobrian opened this issue Oct 23, 2024 · 0 comments
Open

Integrated Migration Suite for Amazon OpenSearch Service #1097

sumobrian opened this issue Oct 23, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@sumobrian
Copy link
Collaborator

Is your feature request related to a problem?

Integrate Migration Products from the Migrations repo into Amazon OpenSearch Service to reduce migration barriers. This integration would enable zero-downtime migrations with the ability to revert changes, ensuring customers can switch and revert workloads without disruptions. The feature is designed not only to improve migration and upgrade reliability but also to enhance user satisfaction and reduce friction for OpenSearch adoption. Users would gain observability into migration progress and status, follow an integrated workflow within Amazon OpenSearch Service, and avoid the need to understand or modify complex network and security configurations to deploy the migration solution.

What solution would you like?

Develop a fully integrated migration workflow within Amazon OpenSearch Service that allows users to seamlessly migrate their workloads with zero downtime. Key features of this solution should include:

  • Built-in Revert Capabilities: Allow the ability to revert migrations if issues are detected, minimizing disruption to production workloads.
  • End-to-End Migration Workflow: Include a guided workflow within the OpenSearch Service console, enabling users to perform migrations without manually configuring complex network settings.
  • Migration Observability: Provide real-time insights and monitoring of migration status and performance, building user confidence in the process and allowing them to proactively address issues. Also, enable a confident switchover to the new target cluster.
  • Migration Multi-Version Hop Support: Allow users to perform multi-version migrations, enabling them to move between multiple versions seamlessly during the migration process.
  • Migrating Additional Features such as Dashboards, Metadata, and Plugins: Expand the migration capabilities to include not only data but also associated features such as dashboards, metadata configurations, and plugins to ensure a complete and consistent migration experience.

What alternatives have you considered?

  1. Manual Migration with Migration Assistant: Users could perform migrations using Migration Assistant, which simplifies the process. However, since it lacks integration with OpenSearch Service, users must understand security and networking implications when deploying migration tooling in their environment, which can introduce complexities beyond their desired involvement.

Do you have any additional context?

Integrating migration products directly into Amazon OpenSearch Service would offer a streamlined, user-friendly experience that minimizes downtime and disruption. This integration would eliminate the need for deep technical knowledge of networking and configurations, enhancing user satisfaction by providing a reliable and consistent zero-downtime migration process. It would ultimately boost OpenSearch adoption by offering a more efficient and operationally optimized solution.

@sumobrian sumobrian added enhancement New feature or request untriaged labels Oct 23, 2024
@sumobrian sumobrian changed the title [FEATURE] Integrating Migration Suite for Amazon OpenSearch Service Integrated Migration Suite for Amazon OpenSearch Service Oct 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Status: 1+ Years
Development

No branches or pull requests

1 participant