AWS solutions documentation change
Summary
Updated guidance for handling type mappings during migration
Security assessment
The change updates documentation references for data transformation without security implications. Focuses on data routing/index naming rather than security controls.
Diff
diff --git a/solutions/latest/migration-assistant-for-amazon-opensearch-service/pb-es68-pilot-config.md b/solutions/latest/migration-assistant-for-amazon-opensearch-service/pb-es68-pilot-config.md index dada8f128..273a75365 100644 --- a//solutions/latest/migration-assistant-for-amazon-opensearch-service/pb-es68-pilot-config.md +++ b//solutions/latest/migration-assistant-for-amazon-opensearch-service/pb-es68-pilot-config.md @@ -84 +84 @@ Set `allowInsecure` to `true` only if the source cluster presents a self-signed -By default, the built-in type-mapping sanitization transformer merges the multiple mapping types found in an Elasticsearch 6.8 index into a single index on the target (union), which is the most common choice when moving off pre-7.0 type mappings. This happens automatically with no configuration field. If you need to route types to separate indexes or drop specific types instead, configure a custom metadata transformer rather than a `multiTypeBehavior` field; see the type-mapping handling guidance in [Use the solution](./use-the-solution.html#getting-started). +By default, the built-in type-mapping sanitization transformer merges the multiple mapping types found in an Elasticsearch 6.8 index into a single index on the target (union), which is the most common choice when moving off pre-7.0 type mappings. This happens automatically with no configuration field. If you need to rename the merged output or drop routed data, configure `TypeMappingSanitizationTransformerProvider` rather than a `multiTypeBehavior` field; see [Transform type mappings](./transform-type-mappings.html).