AWS solutions documentation change
Summary
Updated playbook descriptions: 1) Changed link text from 'Use the solution' to 'Configure and run workflows', 2) Replaced 'Amazon OpenSearch Serverless' with 'Amazon OpenSearch Serverless NextGen' in two migration paths, 3) Enhanced Apache Solr migration description to include live Capture and Replay options, 4) Changed section header from 'Troubleshooting' to 'Run workflows'.
Security assessment
The changes are documentation updates for product naming conventions (adding 'NextGen') and migration capability enhancements. No security vulnerabilities, authentication changes, or security features are mentioned. The SigV4 authentication reference remains unchanged.
Diff
diff --git a/solutions/latest/migration-assistant-for-amazon-opensearch-service/playbooks.md b/solutions/latest/migration-assistant-for-amazon-opensearch-service/playbooks.md index 14ea779b3..a121e0dbe 100644 --- a//solutions/latest/migration-assistant-for-amazon-opensearch-service/playbooks.md +++ b//solutions/latest/migration-assistant-for-amazon-opensearch-service/playbooks.md @@ -9 +9 @@ -Playbooks are end-to-end, copy-pasteable runbooks for specific source-to-target migration paths. Each playbook walks you through a single path from connectivity checks to cutover using the Workflow CLI and supporting `console` commands that run in the Migration Console pod (`migration-console-0`) on Amazon Elastic Kubernetes Service (Amazon EKS). Where the general procedure in [Use the solution](./use-the-solution.html) describes each phase in isolation, a playbook strings those phases together into one ordered sequence tailored to a particular source and target. +Playbooks are end-to-end, copy-pasteable runbooks for specific source-to-target migration paths. Each playbook walks you through a single path from connectivity checks to cutover using the Workflow CLI and supporting `console` commands that run in the Migration Console pod (`migration-console-0`) on Amazon Elastic Kubernetes Service (Amazon EKS). Where the general procedure in [Configure and run workflows](./use-the-solution.html) describes each phase in isolation, a playbook strings those phases together into one ordered sequence tailored to a particular source and target. @@ -22,2 +22,2 @@ Playbook | Migration path | When to use it -[Amazon OpenSearch Service to Amazon OpenSearch Serverless](./playbook-aos-to-serverless.html) | An Amazon OpenSearch Service domain source to an Amazon OpenSearch Serverless collection | Use this when moving an existing Amazon OpenSearch Service domain onto Amazon OpenSearch Serverless. This path uses SigV4 authentication on both clusters (`service: es` for the source domain, `service: aoss` for the target collection) and covers the data access policy mapping that Amazon OpenSearch Serverless requires. -[Apache Solr to Amazon OpenSearch Service](./playbook-solr-to-os3.html) | Apache Solr source to an Amazon OpenSearch Service domain or Amazon OpenSearch Serverless collection | Use this when migrating from Apache Solr. This path is backfill-only: documents are reindexed into the target through RFS. Apache Solr does not support live Capture and Replay, so plan for a write freeze or an external replay mechanism during cutover. +[Amazon OpenSearch Service to Amazon OpenSearch Serverless NextGen](./playbook-aos-to-serverless.html) | An Amazon OpenSearch Service domain source to an Amazon OpenSearch Serverless NextGen collection | Use this when moving an existing Amazon OpenSearch Service domain onto Amazon OpenSearch Serverless NextGen. This path uses SigV4 authentication on both clusters (`service: es` for the source domain, `service: aoss` for the target collection) and covers the data access policy mapping that Amazon OpenSearch Serverless NextGen requires. +[Apache Solr to Amazon OpenSearch Service](./playbook-solr-to-os3.html) | Apache Solr source to an Amazon OpenSearch Service domain or Amazon OpenSearch Serverless NextGen collection | Use this when migrating from Apache Solr. This playbook covers backup-based backfill through RFS. For SolrCloud sources with JSON-format writes, you can add live Capture and Replay with the Solr transform providers described in [Capture and replay live traffic from Solr](./solr-capture-replay.html). @@ -31 +31 @@ To use the Amazon Web Services Documentation, Javascript must be enabled. Please -Troubleshooting +Run workflows