AWS solutions documentation change
Summary
Updated terminology to 'Amazon OpenSearch Serverless NextGen', clarified authentication options and data stream migration process, expanded metadata transformation capabilities, and improved migration planning guidance.
Security assessment
The changes primarily involve product naming updates ('NextGen' suffix), migration process clarifications, and expanded technical capabilities for metadata transformations. While authentication models are mentioned, this is routine documentation of existing options without addressing vulnerabilities. The update to 'no auth' option doesn't indicate a security fix but rather documentation of available configurations.
Diff
diff --git a/solutions/latest/migration-assistant-for-amazon-opensearch-service/plan-your-deployment.md b/solutions/latest/migration-assistant-for-amazon-opensearch-service/plan-your-deployment.md index 13aa04e31..d618dfacf 100644 --- a//solutions/latest/migration-assistant-for-amazon-opensearch-service/plan-your-deployment.md +++ b//solutions/latest/migration-assistant-for-amazon-opensearch-service/plan-your-deployment.md @@ -15 +15 @@ This section describes the assessment, Region, [cost](./cost.html), [security](. -Assessment is where you decide whether your migration to Amazon OpenSearch Service or Amazon OpenSearch Serverless should be simple, staged, or zero-downtime. The goal is not to memorize every breaking change. The goal is to identify the issues that will affect your workflow configuration, your cutover plan, and your application behavior before you start moving data. +Assessment is where you decide whether your migration to Amazon OpenSearch Service or Amazon OpenSearch Serverless NextGen should be simple, staged, or zero-downtime. The goal is not to memorize every breaking change. The goal is to identify the issues that will affect your workflow configuration, your cutover plan, and your application behavior before you start moving data. @@ -27 +27 @@ Before you build the workflow, make sure you can answer: - * What authentication model will be used for source and target — basic auth, AWS Signature Version 4 (SigV4), or both? + * What authentication model will each source and target use - basic auth, AWS Signature Version 4 (SigV4), or no auth? A single cluster `authConfig` uses one mode. @@ -31 +31 @@ Before you build the workflow, make sure you can answer: - * Which components need separate manual migration (security, ISM/ILM, ingest pipelines, OpenSearch Dashboards or Kibana saved objects, data streams)? + * Which components need separate manual migration or preparation (security, ISM/ILM, ingest pipelines, OpenSearch Dashboards or Kibana saved objects, data streams)? @@ -40 +40 @@ Most migration risk falls into four buckets: - * **Application compatibility** — queries, aggregations, index names, aliases, or field names may need to change for the target on Amazon OpenSearch Service or Amazon OpenSearch Serverless. + * **Application compatibility** — queries, aggregations, index names, aliases, or field names may need to change for the target on Amazon OpenSearch Service or Amazon OpenSearch Serverless NextGen. @@ -42 +42 @@ Most migration risk falls into four buckets: - * **Metadata compatibility** — mappings, templates, and settings may need transformations. Built-in transformations cover `string` to `text` and `keyword`, `flattened` to `flat_object`, and `dense_vector` to `knn_vector`. Custom transformers can be supplied through `transformerConfig`. + * **Metadata compatibility** — mappings, templates, and settings may need transformations. Built-in transformations cover multi-type mapping union for legacy Elasticsearch indexes, `string` to `text` and `keyword`, `flattened` to `flat_object`, `dense_vector` to `knn_vector`, k-NN vector compatibility for newer OpenSearch and Serverless targets, and analysis-component cleanup for analyzer, tokenizer, char-filter, and token-filter names that changed across versions. Custom metadata transformers can be supplied through the workflow `metadataTransforms` pipeline or, for raw descriptor configurations, through `transformerConfig`. @@ -53 +53 @@ Most migration risk falls into four buckets: -A migration is only finished when the application behaves correctly on the Amazon OpenSearch Service domain or Amazon OpenSearch Serverless collection. +A migration is only finished when the application behaves correctly on the Amazon OpenSearch Service domain or Amazon OpenSearch Serverless NextGen collection. @@ -82 +82 @@ Aliases | ✓ | Migrated automatically -Data streams | ✗ | Manually recreate on target +Data streams | Partial/manual | Metadata migration does not create data streams. Recreate the target data stream and templates manually; RFS can backfill documents from `.ds-*` backing indexes only when you also configure a backing-index allowlist and data-stream document transform. @@ -105 +105 @@ A migration follows the same lifecycle regardless of source. Use this list to pl - 7. **Cut over** — redirect clients to the Amazon OpenSearch Service domain or Amazon OpenSearch Serverless collection. + 7. **Cut over** — redirect clients to the Amazon OpenSearch Service domain or Amazon OpenSearch Serverless NextGen collection. @@ -114 +114 @@ A migration follows the same lifecycle regardless of source. Use this list to pl -This solution uses Amazon OpenSearch Service and Amazon OpenSearch Serverless, which are not currently available in all AWS Regions. For the most current availability of AWS services by Region, see the [AWS Regional Services List](https://aws.amazon.com/about-aws/global-infrastructure/regional-product-services/). +This solution uses Amazon OpenSearch Service and Amazon OpenSearch Serverless NextGen, which are not currently available in all AWS Regions. For the most current availability of AWS services by Region, see the [AWS Regional Services List](https://aws.amazon.com/about-aws/global-infrastructure/regional-product-services/).