AWS solutions documentation change
Summary
Updated terminology to 'Serverless NextGen', fixed a documentation link, and revised a section header
Security assessment
Changes are purely cosmetic (name updates) and navigational (link updates). No security-related content was added, removed, or modified. Vector query validation guidance remains operational.
Diff
diff --git a/solutions/latest/migration-assistant-for-amazon-opensearch-service/tdvk-application-impact.md b/solutions/latest/migration-assistant-for-amazon-opensearch-service/tdvk-application-impact.md index 49d16b74b..c8a1f48b0 100644 --- a//solutions/latest/migration-assistant-for-amazon-opensearch-service/tdvk-application-impact.md +++ b//solutions/latest/migration-assistant-for-amazon-opensearch-service/tdvk-application-impact.md @@ -9 +9 @@ -The transformation produces a queryable vector index, but k-NN query patterns on Amazon OpenSearch Service and Amazon OpenSearch Serverless can differ from the vector query syntax your application used on Elasticsearch. Plan to review and, where needed, update client query code: +The transformation produces a queryable vector index, but k-NN query patterns on Amazon OpenSearch Service and Amazon OpenSearch Serverless NextGen can differ from the vector query syntax your application used on Elasticsearch. Plan to review and, where needed, update client query code: @@ -15 +15 @@ The transformation produces a queryable vector index, but k-NN query patterns on - * **Query-time embeddings** — As described in [Amazon OpenSearch Serverless considerations](./tdvk-serverless.html), applications that relied on a `model_id` to embed query text on the source may need to embed client-side against the target. + * **Query-time embeddings** — As described in [Amazon OpenSearch Serverless NextGen considerations](./tdvk-serverless.html), applications that relied on a `model_id` to embed query text on the source may need to embed client-side against the target. @@ -20 +20 @@ The transformation produces a queryable vector index, but k-NN query patterns on -Validate these behaviors with representative vector queries in a pilot migration before you cut over production traffic. Use a small index allowlist or a representative non-production subset, as described in [Use the solution](./use-the-solution.html), so you can catch query-compatibility issues early. For the general guidance on validating transformed data against client applications, see [Migrate metadata](./migrate-metadata.html). +Validate these behaviors with representative vector queries in a pilot migration before you cut over production traffic. Use a small index allowlist or a representative non-production subset, as described in [Configure and run workflows](./use-the-solution.html), so you can catch query-compatibility issues early. For the general guidance on validating transformed data against client applications, see [Migrate metadata](./migrate-metadata.html). @@ -28 +28 @@ To use the Amazon Web Services Documentation, Javascript must be enabled. Please -Amazon OpenSearch Serverless considerations +Amazon OpenSearch Serverless NextGen considerations