AWS solutions documentation change
Summary
Updated target name to 'Amazon OpenSearch Serverless NextGen' and added reference to new documentation for handling multi-type mappings.
Security assessment
Changes involve product naming updates and added documentation link for type mapping transformations. No security-related content was modified or added.
Diff
diff --git a/solutions/latest/migration-assistant-for-amazon-opensearch-service/playbook-es68-to-os3.md b/solutions/latest/migration-assistant-for-amazon-opensearch-service/playbook-es68-to-os3.md index a5f726590..7d08f655c 100644 --- a//solutions/latest/migration-assistant-for-amazon-opensearch-service/playbook-es68-to-os3.md +++ b//solutions/latest/migration-assistant-for-amazon-opensearch-service/playbook-es68-to-os3.md @@ -11 +11 @@ This playbook is an end-to-end runbook for migrating a self-managed Elasticsearc -Migration Assistant takes a one-time snapshot of the source cluster, migrates index metadata, and uses Reindex-from-Snapshot (RFS) to bulk-index documents into the Amazon OpenSearch Service domain or Amazon OpenSearch Serverless collection. Because Elasticsearch 6.x indexes can contain multiple mapping types and OpenSearch does not, multi-type (pre-7.0) mappings are resolved automatically by the built-in type-mapping sanitization transformer, which merges the multiple types into a single index (union) by default. You do not configure this behavior with a field in the workflow configuration; to route or split types differently, supply a custom metadata transformer instead. +Migration Assistant takes a one-time snapshot of the source cluster, migrates index metadata, and uses Reindex-from-Snapshot (RFS) to bulk-index documents into the Amazon OpenSearch Service domain or Amazon OpenSearch Serverless NextGen collection. Because Elasticsearch 6.x indexes can contain multiple mapping types and OpenSearch does not, multi-type (pre-7.0) mappings are resolved automatically by the built-in type-mapping sanitization transformer, which merges the multiple types into a single index (union) by default. You do not configure this behavior with a field in the workflow configuration; if you need a different post-union rename, merge, or drop pattern, see [Transform type mappings](./transform-type-mappings.html).