AWS solutions documentation change
Summary
Updated solution overview with new AI-assisted migration option, clarified migration paths including OpenSearch Serverless NextGen, added version compatibility notes, restructured content flow with new operating modes, and updated references.
Security assessment
The changes focus on feature enhancements (AI-assisted migration), product naming updates (Serverless NextGen), and documentation restructuring. No security vulnerabilities, configurations, or security-related features are mentioned. Changes are operational improvements without security implications.
Diff
diff --git a/solutions/latest/migration-assistant-for-amazon-opensearch-service/solution-overview.md b/solutions/latest/migration-assistant-for-amazon-opensearch-service/solution-overview.md index d7a626724..3cbab1ce8 100644 --- a//solutions/latest/migration-assistant-for-amazon-opensearch-service/solution-overview.md +++ b//solutions/latest/migration-assistant-for-amazon-opensearch-service/solution-overview.md @@ -9 +9 @@ -OpenSearch is widely adopted for log analytics and search functionalities. However, self-managing OpenSearch can be operationally demanding. Amazon OpenSearch Service and Amazon OpenSearch Serverless offer more manageable alternatives, but transitioning to these services or updating to the latest OpenSearch version has historically been complex. Also, it can be difficult for a customer to predict the outcome of a migration. The Migration Assistant for Amazon OpenSearch Service solution addresses these challenges - it simplifies the migration process, ensures integrity, and validates performance post-migration. +###### Tip @@ -11 +11,5 @@ OpenSearch is widely adopted for log analytics and search functionalities. Howev -The Migration Assistant for Amazon OpenSearch Service solution is a workflow-driven toolkit designed to ease the transition to Amazon OpenSearch Service and Amazon OpenSearch Serverless, facilitate upgrades to the latest OpenSearch versions, and refine cluster configurations based on observed traffic patterns. Migration Assistant 3.0 deploys to Amazon Elastic Kubernetes Service (Amazon EKS) and runs migrations as Kubernetes-managed workloads. Whether you’re looking to set up a proof-of-concept in AWS, transition production workloads with confidence, or enhance your current OpenSearch clusters, this guide provides step-by-step instructions, best practices, and insights to help you migrate to Amazon OpenSearch Service or Amazon OpenSearch Serverless. +For a guided, conversational experience that handles configuration generation, schema extraction, and troubleshooting automatically, use Migration Assistant AI agent mode. See [AI-assisted migration](./agent-assisted-migration.html). + +OpenSearch is widely adopted for log analytics and search. However, self-managing OpenSearch can be operationally demanding. Amazon OpenSearch Service and Amazon OpenSearch Serverless NextGen offer more manageable alternatives, but transitioning to these services or updating to the latest OpenSearch version has historically been complex. It can also be difficult to predict the outcome of a migration before production traffic moves. The Migration Assistant for Amazon OpenSearch Service solution addresses these challenges by making migration workflow-driven, repeatable, and easier to validate before cutover. + +The Migration Assistant for Amazon OpenSearch Service solution is a workflow-driven toolkit designed to ease the transition to Amazon OpenSearch Service and Amazon OpenSearch Serverless NextGen, facilitate upgrades to the latest OpenSearch versions, and refine cluster configurations based on observed traffic patterns. Migration Assistant 3.0 deploys to Amazon Elastic Kubernetes Service (Amazon EKS) and runs migrations as Kubernetes-managed workloads. Whether you’re looking to set up a proof-of-concept in AWS, transition production workloads with confidence, or enhance your current OpenSearch clusters, this guide provides step-by-step instructions, best practices, and insights to help you migrate to Amazon OpenSearch Service or Amazon OpenSearch Serverless NextGen. @@ -15 +19 @@ The Migration Assistant for Amazon OpenSearch Service solution is a workflow-dri -The following matrix shows which source versions can be directly migrated to which Amazon OpenSearch Service or Amazon OpenSearch Serverless target versions: +The following matrix shows which source versions can be directly migrated to which Amazon OpenSearch Service or Amazon OpenSearch Serverless NextGen target versions: @@ -17 +21 @@ The following matrix shows which source versions can be directly migrated to whi -Source version | OpenSearch 1.x | OpenSearch 2.x | OpenSearch 3.x | Amazon OpenSearch Serverless +Source version | OpenSearch 1.x | OpenSearch 2.x | OpenSearch 3.x | Amazon OpenSearch Serverless NextGen @@ -23 +27,6 @@ OpenSearch 1.x–2.x | | ✓ | ✓ | ✓** -Apache Solr 6.x–9.x | | | ✓* | ✓* +OpenSearch 3.x | | | ✓ | ✓** +Apache Solr 6.x–9.x | | | ✓***** | ✓***** + +###### Note + +* Elasticsearch 1.x–2.x migrations are backfill only. Live traffic capture and replay is not supported for those source versions. @@ -27 +36 @@ Apache Solr 6.x–9.x | | | ✓* | ✓* -* Backfill only — Live traffic capture and replay is not supported for these source versions. +** Live traffic capture and replay is supported with Amazon OpenSearch Serverless NextGen targets when the source supports it. Document IDs are preserved on `SEARCH` collections. `TIMESERIES` and `VECTORSEARCH` collections use server-generated IDs, so replay cannot reconcile updates or deletes by source `_id` on those collection types. @@ -31 +40,12 @@ Apache Solr 6.x–9.x | | | ✓* | ✓* -** Live traffic capture and replay is supported with Amazon OpenSearch Serverless targets when the source supports it. Document IDs are preserved only on `SEARCH` collection types; `TIMESERIES` and `VECTORSEARCH` collection types use server-generated IDs. +***** Backfill and live traffic capture and replay are supported for Apache Solr sources running in SolrCloud mode. Capture and replay requires JSON-format write requests. See [Capture and replay live traffic from Solr](./solr-capture-replay.html). + +**Get started** + +Migration Assistant includes two operating modes: an AI-assisted agent and a manual Workflow CLI. Choose the path that matches how much guidance and automation you want during assessment, deployment, workflow configuration, and migration. + +Path | Use when | Start here +---|---|--- +AI-assisted migration | You want a guided, conversational experience that can help assess your source cluster, deploy Migration Assistant, generate workflow configuration, run the migration, and troubleshoot issues. | [AI-assisted migration](./agent-assisted-migration.html) +Manual Workflow CLI | You want direct control over deployment, workflow JSON, CLI commands, approval gates, validation, and operational troubleshooting. | [Prepare for migration](./prepare-for-migration.html) + +If this is your first migration, start with [AI-assisted migration](./agent-assisted-migration.html). The agent can guide you through assessment, deployment, configuration, and execution. If you prefer to operate each step yourself, start with [Prepare for migration](./prepare-for-migration.html) and then use the manual workflow path in [Run workflows](./use-the-solution.html). @@ -37 +57 @@ Apache Solr 6.x–9.x | | | ✓* | ✓* - * Migrate existing data from legacy Elasticsearch, OpenSearch, and Apache Solr clusters to Amazon OpenSearch Service domains and Amazon OpenSearch Serverless collections. + * Migrate existing data from legacy Elasticsearch, OpenSearch, and Apache Solr clusters to Amazon OpenSearch Service domains and Amazon OpenSearch Serverless NextGen collections. @@ -39 +59,3 @@ Apache Solr 6.x–9.x | | | ✓* | ✓* - * Intercept and redirect live traffic from self-managed Elasticsearch or OpenSearch clusters to Amazon OpenSearch Service domains and Amazon OpenSearch Serverless collections with minimal latency. + * Use AI-assisted migration to guide source assessment, deployment, workflow generation, migration execution, and troubleshooting. + + * Intercept and redirect live traffic from supported self-managed Elasticsearch, OpenSearch, and SolrCloud sources to Amazon OpenSearch Service domains and Amazon OpenSearch Serverless NextGen collections with minimal latency. @@ -54 +76 @@ Apache Solr 6.x–9.x | | | ✓* | ✓* -This implementation guide provides an overview of the Migration Assistant for Amazon OpenSearch Service solution, its reference architecture and components, considerations for planning the deployment, and configuration steps for deploying the solution to the Amazon Web Services (AWS) Cloud. It also references the solution’s open-source documentation on [GitHub](https://github.com/opensearch-project/opensearch-migrations), which includes developer documentation and tips to enhance and contribute to the solution. +This implementation guide provides an overview of the Migration Assistant for Amazon OpenSearch Service solution, its reference architecture and components, considerations for planning the deployment, and configuration steps for deploying the solution to the Amazon Web Services (AWS) Cloud. It also references the solution’s open-source documentation, which includes developer documentation and tips to enhance and contribute to the solution. @@ -58 +80,14 @@ The intended audience for using this solution’s features and capabilities in t -Use this navigation table to quickly find answers to these questions: +To follow the migration story end to end, read this guide in this order: + + 1. Solution overview - confirm the supported migration path and core concepts. + + 2. [Prepare for migration](./prepare-for-migration.html) \- understand the architecture, plan the deployment, and deploy Migration Assistant. + + 3. [Run a migration](./run-a-migration.html) \- configure workflows, follow a playbook, migrate data, replay traffic, monitor progress, troubleshoot issues, cut over, and remove the solution after the rollback window. + + 4. [Reference](./reference.html) \- review source, release, legal, and data-collection reference material. + + + + +For specific planning and reference questions, use the following table: @@ -62 +97 @@ If you want to . . . | Read . . . -Know the cost for running this solution. The estimated cost for running this solution in the US East (N. Virginia) Region is approximately USD $3,096 for a 15-day migration with 100 TB of existing data and 15 MBps of live traffic. | [Cost](./cost.html) +Know the cost for running this solution. Costs depend on migration duration, data volume, target type, and whether you run capture and replay. For current sample estimates, see [Cost](./cost.html). | [Cost](./cost.html) @@ -72 +107 @@ View or download the AWS CloudFormation template included in this solution to au -Access the source code and optionally use the AWS Cloud Development Kit (AWS CDK) to deploy the solution. | [GitHub repository](https://github.com/opensearch-project/opensearch-migrations) +Access the source code and optionally use the AWS Cloud Development Kit (AWS CDK) to deploy the solution. | [Migration Assistant documentation](https://docs.aws.amazon.com/solutions/migration-assistant-for-amazon-opensearch-service/)