AWS solutions documentation change
Summary
Rebranded 'Metadata Migration Tool' to 'Metadata Migration', integrated it into workflow phases, added type transformation details, and explicitly called out non-migrated elements including security configurations.
Security assessment
While the change mentions security configurations as non-migrated items, this is a functional limitation disclosure rather than a security fix or feature documentation. No vulnerability remediation or security enhancement is described.
Diff
diff --git a/solutions/latest/migration-assistant-for-amazon-opensearch-service/metadata-migration-tool-1.md b/solutions/latest/migration-assistant-for-amazon-opensearch-service/metadata-migration-tool-1.md index 2a05dfb9b..1365c9e9f 100644 --- a//solutions/latest/migration-assistant-for-amazon-opensearch-service/metadata-migration-tool-1.md +++ b//solutions/latest/migration-assistant-for-amazon-opensearch-service/metadata-migration-tool-1.md @@ -7 +7 @@ -# Metadata Migration Tool +# Metadata Migration @@ -9 +9 @@ -The Metadata Migration Tool migrates templates and indices in a specified snapshot of a source cluster to a target cluster. It parses the contents of the snapshot to extract the settings and configuration of the templates, aliases, and indices in the snapshot. Then it migrates the settings and configuration to the target cluster. The user can apply allowlists to filter which templates and indices are migrated. If a template or index of the same name already exists on the target cluster, this tool doesn’t overwrite the existing one on the target. Instead, the tool leaves the pre-existing index and template settings as-is without modifications. +Metadata migration moves the Amazon OpenSearch Service domain or Amazon OpenSearch Serverless collection into a shape that can accept the incoming data and traffic. It handles mappings, templates, aliases, and other index-level definitions before document backfill or replay becomes meaningful. In the workflow model, metadata migration is a configured phase inside the migration workflow, not a separate manual tool run. When `metadataMigrationConfig` is present, the workflow runs two logical steps: `evaluateMetadata` (evaluates what would be applied) and `migrateMetadata` (writes those changes to the target). If approvals are enabled, the workflow can pause between these steps so you can inspect the result before continuing. @@ -11 +11,3 @@ The Metadata Migration Tool migrates templates and indices in a specified snapsh -The tool also applies basic transformations to the template and index settings to handle upgrades between version-specific behavior. See the [Metadata Migration Tool README](https://github.com/opensearch-project/opensearch-migrations/blob/main/MetadataMigration/README.md) for more information. +Metadata migration handles index settings, index mappings, legacy and composable templates, component templates, and aliases. It also applies built-in transformations to handle upgrades between version-specific behavior, including `string` to `text` and `keyword`, `flattened` to `flat_object`, and `dense_vector` to `knn_vector` (with additional vector compatibility transformations for newer Amazon OpenSearch Service and Amazon OpenSearch Serverless targets). Advanced users can also supply custom metadata transformers through `transformerConfig`, `transformerConfigBase64`, or `transformerConfigFile`. + +Plan separate work for security configuration, ISM/ILM policies, ingest pipelines, OpenSearch Dashboards or Kibana saved objects, data streams, and cluster-level tuning — these are not migrated automatically. @@ -19 +21 @@ To use the Amazon Web Services Documentation, Javascript must be enabled. Please -Application Load Balancer +Capture Proxy Service on Amazon EKS