AWS solutions documentation change
Summary
Updated product name from 'Amazon OpenSearch Serverless' to 'Amazon OpenSearch Serverless NextGen' throughout the document. Added 'NextGen' suffix to all references.
Security assessment
Changes are purely branding/nomenclature updates without any modifications to security content. The existing security explanation about SigV4 authentication and IAM remains unchanged.
Diff
diff --git a/solutions/latest/migration-assistant-for-amazon-opensearch-service/playbook-aos-to-serverless.md b/solutions/latest/migration-assistant-for-amazon-opensearch-service/playbook-aos-to-serverless.md index e0445bd0d..acf26d1d7 100644 --- a//solutions/latest/migration-assistant-for-amazon-opensearch-service/playbook-aos-to-serverless.md +++ b//solutions/latest/migration-assistant-for-amazon-opensearch-service/playbook-aos-to-serverless.md @@ -7 +7 @@ -# Playbook: Amazon OpenSearch Service to Amazon OpenSearch Serverless +# Playbook: Amazon OpenSearch Service to Amazon OpenSearch Serverless NextGen @@ -9 +9 @@ -This playbook is an end-to-end runbook for migrating an existing [Amazon OpenSearch Service](https://aws.amazon.com/opensearch-service) domain to an [Amazon OpenSearch Serverless](https://aws.amazon.com/opensearch-service/features/serverless) collection, using a vector-search workload as the worked example. For a small domain — a handful of vector indexes totaling a few tens of gigabytes — plan for roughly 90 minutes end to end, most of which is unattended snapshot and backfill time. +This playbook is an end-to-end runbook for migrating an existing [Amazon OpenSearch Service](https://aws.amazon.com/opensearch-service) domain to an [Amazon OpenSearch Serverless NextGen](https://aws.amazon.com/opensearch-service/features/serverless) collection, using a vector-search workload as the worked example. For a small domain — a handful of vector indexes totaling a few tens of gigabytes — plan for roughly 90 minutes end to end, most of which is unattended snapshot and backfill time. @@ -11 +11 @@ This playbook is an end-to-end runbook for migrating an existing [Amazon OpenSea -This is a backfill-style migration: Reindex-from-Snapshot (RFS) takes a point-in-time snapshot of the source domain, migrates metadata, and bulk-indexes documents into the collection. Amazon OpenSearch Serverless does not accept snapshot restores, ISM/ILM policies, ingest pipelines, custom plugins, or `_cluster/settings` changes, so the runbook below builds the collection’s shape with security policies and metadata migration rather than a restore. For the broader conceptual comparison, see [Migrate to Amazon OpenSearch Serverless](./migrate-to-serverless.html). +This is a backfill-style migration: Reindex-from-Snapshot (RFS) takes a point-in-time snapshot of the source domain, migrates metadata, and bulk-indexes documents into the collection. Amazon OpenSearch Serverless NextGen does not accept snapshot restores, ISM/ILM policies, ingest pipelines, custom plugins, or `_cluster/settings` changes, so the runbook below builds the collection’s shape with security policies and metadata migration rather than a restore. For the broader conceptual comparison, see [Migrate to Amazon OpenSearch Serverless NextGen](./migrate-to-serverless.html). @@ -13 +13 @@ This is a backfill-style migration: Reindex-from-Snapshot (RFS) takes a point-in -For an at-a-glance summary of how Amazon OpenSearch Serverless constrains a migration, read the [How Serverless differs](./pb-aoss-how-serverless-differs.html) callout before you begin. +For an at-a-glance summary of how Amazon OpenSearch Serverless NextGen constrains a migration, read the [How Serverless differs](./pb-aoss-how-serverless-differs.html) callout before you begin. @@ -17 +17 @@ For an at-a-glance summary of how Amazon OpenSearch Serverless constrains a migr -Amazon OpenSearch Serverless authenticates every request with AWS Signature Version 4 (SigV4) — there is no basic-auth or fine-grained access control (FGAC) username and password on the target. Both the snapshot source access and the migration’s write access to the collection are governed by [AWS Identity and Access Management](https://aws.amazon.com/iam) (IAM) and by the collection’s data access policy. +Amazon OpenSearch Serverless NextGen authenticates every request with AWS Signature Version 4 (SigV4) — there is no basic-auth or fine-grained access control (FGAC) username and password on the target. Both the snapshot source access and the migration’s write access to the collection are governed by [AWS Identity and Access Management](https://aws.amazon.com/iam) (IAM) and by the collection’s data access policy.