AWS solutions documentation change
Summary
Updated terminology from 'Amazon OpenSearch Serverless collection' to 'Amazon OpenSearch Serverless NextGen collection' in two instances
Security assessment
The change only updates product naming conventions without modifying security configurations, access controls, or vulnerability information. No security implications were introduced.
Diff
diff --git a/solutions/latest/migration-assistant-for-amazon-opensearch-service/switch-traffic.md b/solutions/latest/migration-assistant-for-amazon-opensearch-service/switch-traffic.md index 4c8877e8a..37e97a2f1 100644 --- a//solutions/latest/migration-assistant-for-amazon-opensearch-service/switch-traffic.md +++ b//solutions/latest/migration-assistant-for-amazon-opensearch-service/switch-traffic.md @@ -9 +9 @@ -Switching traffic is the cutover step that completes every migration scenario. This phase moves clients off the source and onto the Amazon OpenSearch Service domain or Amazon OpenSearch Serverless collection while keeping a rollback path available. +Switching traffic is the cutover step that completes every migration scenario. This phase moves clients off the source and onto the Amazon OpenSearch Service domain or Amazon OpenSearch Serverless NextGen collection while keeping a rollback path available. @@ -11 +11 @@ Switching traffic is the cutover step that completes every migration scenario. T -For backfill-only migrations (Scenario 1), there is no capture proxy and no replay. Cut over after backfill and validation complete, repointing clients directly from the source to the Amazon OpenSearch Service domain or Amazon OpenSearch Serverless collection. The capture-proxy and replay preconditions described in this chapter apply only to capture-and-replay (Scenario 2) and zero-downtime (Scenario 3) migrations. See [Migration scenarios](./use-the-solution.html#migration-scenarios). +For backfill-only migrations (Scenario 1), there is no capture proxy and no replay. Cut over after backfill and validation complete, repointing clients directly from the source to the Amazon OpenSearch Service domain or Amazon OpenSearch Serverless NextGen collection. The capture-proxy and replay preconditions described in this chapter apply only to capture-and-replay (Scenario 2) and zero-downtime (Scenario 3) migrations. See [Migration scenarios](./use-the-solution.html#migration-scenarios).