diff --git a/.github/vale/styles/Vocab/OpenSearch/Products/accept.txt b/.github/vale/styles/Vocab/OpenSearch/Products/accept.txt index b64c544b468..cddf410be54 100644 --- a/.github/vale/styles/Vocab/OpenSearch/Products/accept.txt +++ b/.github/vale/styles/Vocab/OpenSearch/Products/accept.txt @@ -3,6 +3,7 @@ Adoptium AI21 Labs Jurassic Amazon Amazon OpenSearch Serverless +Amazon OpenSearch Serverless NextGen Amazon OpenSearch Service Amazon Bedrock Amazon Kinesis diff --git a/_migration-assistant/amazon-opensearch-serverless.md b/_migration-assistant/amazon-opensearch-serverless.md index a9c5f7cd5c6..50a9b4a0e0f 100644 --- a/_migration-assistant/amazon-opensearch-serverless.md +++ b/_migration-assistant/amazon-opensearch-serverless.md @@ -1,13 +1,13 @@ --- layout: default -title: Migrate to OpenSearch Serverless +title: Migrate to OpenSearch Serverless NextGen nav_order: 55 permalink: /migration-assistant/amazon-opensearch-serverless/ --- -# Migrate to OpenSearch Serverless +# Migrate to OpenSearch Serverless NextGen -If your target is an Amazon OpenSearch Serverless collection, Serverless works as a target for every source Migration Assistant supports: Elasticsearch 1.x--2.x, OpenSearch 1.x--2.x, Amazon OpenSearch Service, and Apache Solr 6.x--9.x (backfill only). The migration steps are the same as for any other OpenSearch target. Follow your source's playbook and use the Serverless-specific target configuration from this page. +If your target is an Amazon OpenSearch Serverless NextGen collection, Serverless NextGen works as a target for every source Migration Assistant supports: Elasticsearch 1.x--2.x, OpenSearch 1.x--2.x, Amazon OpenSearch Service, and Apache Solr 6.x--9.x (backfill only). The migration steps are the same as for any other OpenSearch target. Follow your source's playbook and use the Serverless NextGen target configuration from this page. | Source | Backfill | Capture and Replay | |:-------|:--------:|:------------------:| @@ -19,21 +19,21 @@ If your target is an Amazon OpenSearch Serverless collection, Serverless works a ## Collection types -Amazon OpenSearch Serverless supports the following collection types. Migration Assistant auto-detects the collection type and adjusts behavior accordingly. +Amazon OpenSearch Serverless NextGen supports the following collection types. Migration Assistant auto-detects the collection type and adjusts behavior accordingly. | Collection type | Document IDs | |:---------------|:------------| | `SEARCH` | Preserves source document IDs | -| `TIMESERIES` | Server-generated IDs (source IDs not preserved) | +| `TIMESERIES` | Server-generated IDs (source IDs not preserved). Not supported on NextGen at launch (available with Classic). | | `VECTORSEARCH` | Server-generated IDs (source IDs not preserved) | If your source data relies on specific document IDs (for example, for lookups or deduplication), use a `SEARCH` collection. -When migrating to a `VECTORSEARCH` collection, `knn_vector` field mappings are automatically converted to Faiss HNSW for Serverless compatibility, and `model_id` references are removed (Serverless does not support training APIs). +When migrating to a `VECTORSEARCH` collection, `knn_vector` field mappings are automatically converted to Faiss HNSW for Serverless NextGen compatibility, and `model_id` references are removed (Amazon OpenSearch Serverless NextGen does not support training APIs). ## Connecting your collection to Migration Assistant -Migration Assistant requires the following configuration to access your OpenSearch Serverless collection: +Migration Assistant requires the following configuration to access your Amazon OpenSearch Serverless NextGen collection: 1. The migration IAM role must have `aoss:APIAccessAll` in its IAM policy (the Amazon Elastic Kubernetes Service (EKS) deployment handles this automatically). 2. The migration IAM role must be listed as a `Principal` in your collection's data access policy (you must configure this). @@ -94,7 +94,7 @@ If your collection already has a data access policy, use `update-access-policy` ### Step 3: Configure the workflow -Configure your OpenSearch Serverless collection as the target in your workflow configuration. The key difference from a managed OpenSearch Service target is `service: aoss` (instead of `service: es`): +Configure your Amazon OpenSearch Serverless NextGen collection as the target in your workflow configuration. The key difference from a managed OpenSearch Service target is `service: aoss` (instead of `service: es`): ```bash workflow configure edit @@ -107,7 +107,7 @@ Set the target cluster: { "targetClusters": { "target": { - "endpoint": "https://..aoss.amazonaws.com", + "endpoint": "https://.aoss..on.aws", "authConfig": { "sigv4": { "region": "", @@ -126,6 +126,6 @@ Then follow the steps in [Using the Workflow CLI]({{site.url}}{{site.baseurl}}/m Choose the playbook for your source type: -- **Self-managed/third-party Elasticsearch or OpenSearch** -- Follow the [Elasticsearch 6.8 → OpenSearch 3.5 playbook]({{site.url}}{{site.baseurl}}/migration-assistant/playbook-elasticsearch-6-8-to-opensearch-3/), then replace the target cluster block with the preceding OpenSearch Serverless configuration. -- **Amazon OpenSearch Service/legacy Elasticsearch Service** -- Follow the [Amazon OpenSearch Service → Amazon OpenSearch Serverless playbook]({{site.url}}{{site.baseurl}}/migration-assistant/playbook-amazon-opensearch-service-to-serverless/). -- **Apache Solr** -- Follow the [Apache Solr 8.11 → OpenSearch 3.5 playbook]({{site.url}}{{site.baseurl}}/migration-assistant/playbook-solr-8.11-to-opensearch-3/), then replace the target cluster block with the preceding OpenSearch Serverless configuration. +- **Self-managed/third-party Elasticsearch or OpenSearch** -- Follow the [Elasticsearch 6.8 → OpenSearch 3.5 playbook]({{site.url}}{{site.baseurl}}/migration-assistant/playbook-elasticsearch-6-8-to-opensearch-3/), then replace the target cluster block with the preceding Serverless NextGen configuration. +- **Amazon OpenSearch Service/legacy Elasticsearch Service** -- Follow the [Amazon OpenSearch Service → Amazon OpenSearch Serverless NextGen playbook]({{site.url}}{{site.baseurl}}/migration-assistant/playbook-amazon-opensearch-service-to-serverless/). +- **Apache Solr** -- Follow the [Apache Solr 8.11 → OpenSearch 3.5 playbook]({{site.url}}{{site.baseurl}}/migration-assistant/playbook-solr-8.11-to-opensearch-3/), then replace the target cluster block with the preceding Serverless NextGen configuration. diff --git a/_migration-assistant/is-migration-assistant-right-for-you.md b/_migration-assistant/is-migration-assistant-right-for-you.md index a4f072a7a3c..4f60c2d3075 100644 --- a/_migration-assistant/is-migration-assistant-right-for-you.md +++ b/_migration-assistant/is-migration-assistant-right-for-you.md @@ -59,7 +59,7 @@ The following table lists supported source and target platforms. |:---------|:-------|:-------| | Self-managed (on-premises) | Yes | Yes | | Amazon OpenSearch Service | Yes | Yes | -| [Amazon OpenSearch Serverless]({{site.url}}{{site.baseurl}}/migration-assistant/amazon-opensearch-serverless/) | No | Yes | +| [Amazon OpenSearch Serverless NextGen]({{site.url}}{{site.baseurl}}/migration-assistant/amazon-opensearch-serverless/) | No | Yes | | Third-party cloud providers | Yes | Yes | | AWS EC2 | Yes | Yes | | Apache Solr (SolrCloud/Standalone) | Yes | No | diff --git a/_migration-assistant/migration-phases/deploy/deploying-to-kubernetes.md b/_migration-assistant/migration-phases/deploy/deploying-to-kubernetes.md index 918d3df3ee1..220b7457562 100644 --- a/_migration-assistant/migration-phases/deploy/deploying-to-kubernetes.md +++ b/_migration-assistant/migration-phases/deploy/deploying-to-kubernetes.md @@ -198,11 +198,11 @@ Migration Assistant supports the following authentication methods on generic Kub Basic authentication works the same way as EKS. Put the credentials in a Kubernetes secret and reference the secret name in `authConfig.basic.secretName`. -### Use AWS Signature Version 4 for Amazon OpenSearch Service or Serverless +### Use AWS Signature Version 4 for Amazon OpenSearch Service or Serverless NextGen AWS Signature Version 4 is supported by the workflow configuration, but **generic Kubernetes does not automatically create AWS pod identity for you**. -If your source or target uses Amazon OpenSearch Service or OpenSearch Serverless, you must make AWS credentials available to two sets of pods: +If your source or target uses Amazon OpenSearch Service or OpenSearch Serverless NextGen, you must make AWS credentials available to two sets of pods: - The Migration Console pod (`migration-console-0`), running under the `migration-console-access-role` service account, which runs CLI commands such as `console clusters connection-check` - The Argo workflow executor pods, running under the `argo-workflow-executor` service account, which perform the actual migration steps. diff --git a/_migration-assistant/migration-phases/migrate-metadata/handling-field-type-breaking-changes.md b/_migration-assistant/migration-phases/migrate-metadata/handling-field-type-breaking-changes.md index e94a4bffe6c..cd09c3a72ba 100644 --- a/_migration-assistant/migration-phases/migrate-metadata/handling-field-type-breaking-changes.md +++ b/_migration-assistant/migration-phases/migrate-metadata/handling-field-type-breaking-changes.md @@ -21,7 +21,7 @@ Before you build custom logic, verify whether the migration is already covered b - `string` to `text` and `keyword` - `flattened` to `flat_object` - `dense_vector` to `knn_vector` -- Additional vector compatibility adjustments for newer OpenSearch and Serverless targets. +- Additional vector compatibility adjustments for newer OpenSearch and Serverless NextGen targets. ## Custom field type transformer diff --git a/_migration-assistant/migration-phases/migrate-metadata/index.md b/_migration-assistant/migration-phases/migrate-metadata/index.md index 2d76421a8e9..ab8adad6137 100644 --- a/_migration-assistant/migration-phases/migrate-metadata/index.md +++ b/_migration-assistant/migration-phases/migrate-metadata/index.md @@ -46,7 +46,7 @@ The current metadata migration path already includes built-in transformations fo - `string` to `text` and `keyword` - `flattened` to `flat_object` - `dense_vector` to `knn_vector` -- Additional vector compatibility transformations for newer OpenSearch and Serverless targets. +- Additional vector compatibility transformations for newer OpenSearch and Serverless NextGen targets. If your migration needs more than the built-ins, you can also supply custom metadata transformers through `transformerConfig`, `transformerConfigBase64`, or `transformerConfigFile`. diff --git a/_migration-assistant/migration-phases/migrate-metadata/transform-dense-vector-knn-vector.md b/_migration-assistant/migration-phases/migrate-metadata/transform-dense-vector-knn-vector.md index 728ae68d0f5..c364c9369bd 100644 --- a/_migration-assistant/migration-phases/migrate-metadata/transform-dense-vector-knn-vector.md +++ b/_migration-assistant/migration-phases/migrate-metadata/transform-dense-vector-knn-vector.md @@ -19,7 +19,7 @@ The metadata migration path can: - Translate vector dimensions and related settings. - Prepare the target mapping for OpenSearch vector search. -Depending on the target, additional vector compatibility transforms may also apply, including Serverless-specific adjustments. +Depending on the target, additional vector compatibility transforms may also apply, including Serverless NextGen-specific adjustments. ## Identifying dense_vector fields @@ -52,6 +52,6 @@ Even when the mapping migration succeeds, query behavior may still need to chang Run a pilot migration with representative queries before cutover in the following cases: -- The target is OpenSearch Serverless. +- The target is Amazon OpenSearch Serverless NextGen. - The target version has vector-engine compatibility constraints. - The application relies on specific vector query syntax or ranking behavior. diff --git a/_migration-assistant/playbook-amazon-opensearch-service-to-serverless.md b/_migration-assistant/playbook-amazon-opensearch-service-to-serverless.md index 35e5b158bcf..6d3dfa65cb8 100644 --- a/_migration-assistant/playbook-amazon-opensearch-service-to-serverless.md +++ b/_migration-assistant/playbook-amazon-opensearch-service-to-serverless.md @@ -1,16 +1,16 @@ --- layout: default -title: "Amazon OpenSearch Service → Amazon OpenSearch Serverless" +title: "Amazon OpenSearch Service → Amazon OpenSearch Serverless NextGen" nav_order: 2 parent: Playbooks permalink: /migration-assistant/playbook-amazon-opensearch-service-to-serverless/ --- -# Playbook: Amazon OpenSearch Service to Amazon OpenSearch Serverless (vector search) +# Playbook: Amazon OpenSearch Service to Amazon OpenSearch Serverless NextGen (vector search) -This playbook describes migrating an Amazon OpenSearch Service domain running Elasticsearch 7.10 to an Amazon OpenSearch Serverless vector search collection using Migration Assistant. +This playbook describes migrating an Amazon OpenSearch Service domain running Elasticsearch 7.10 to an Amazon OpenSearch Serverless NextGen vector search collection using Migration Assistant. -OpenSearch Serverless with the `VECTORSEARCH` collection type provides the following benefits: +Amazon OpenSearch Serverless NextGen with the `VECTORSEARCH` collection type provides the following benefits: - **No cluster management** -- No nodes to size, patch, or scale. AWS manages capacity automatically. - **Built-in vector engine** -- Designed for k-NN search, semantic search, and retrieval-augmented generation (RAG) workloads. @@ -18,14 +18,14 @@ OpenSearch Serverless with the `VECTORSEARCH` collection type provides the follo - **Automatic scaling** -- Scales indexing and search capacity independently based on demand. - **Built-in encryption and access control** -- Encryption at rest, in transit, and fine-grained data access policies without managing security plugins. -If you are running vector or k-NN workloads on an Amazon OpenSearch Service domain, Serverless eliminates the need to manually select and scale instance types for vector workloads, which are memory- and compute-intensive. +If you are running vector or k-NN workloads on an Amazon OpenSearch Service domain, Serverless NextGen eliminates the need to manually select and scale instance types for vector workloads, which are memory- and compute-intensive. {: .note } -## OpenSearch Service compared to OpenSearch Serverless +## OpenSearch Service compared to OpenSearch Serverless NextGen -The following table lists key differences between Amazon OpenSearch Service and OpenSearch Serverless. +The following table lists key differences between Amazon OpenSearch Service and Amazon OpenSearch Serverless NextGen. -| Feature | Amazon OpenSearch Service | OpenSearch Serverless | +| Feature | Amazon OpenSearch Service | Amazon OpenSearch Serverless NextGen | |:---------|:---------------------------|:----------------------| | Cluster settings | Full `_cluster/settings` API | Not supported | | Snapshot/restore | Supported | Not supported (use Migration Assistant backfill) | @@ -51,7 +51,7 @@ The following table lists the example values used in this playbook. | Region | `us-east-2` | | AWS Identity and Access Management (IAM) role | Admin | | Source | Amazon OpenSearch Service domain (`my-source-domain`, Elasticsearch 7.10) | -| Target | Amazon OpenSearch Serverless collection (`my-target-collection`, VECTORSEARCH) | +| Target | Amazon OpenSearch Serverless NextGen collection (`my-target-collection`, VECTORSEARCH) | | Deployment | "Launch into existing virtual private cloud (VPC)" CloudFormation template | | Stage | `dev` | @@ -64,7 +64,7 @@ The following table provides approximate durations for each phase of the migrati | Phase | Duration | |-------|----------| -| Prerequisites (Amazon OpenSearch Serverless collection, policies, IAM, VPC peering) | 15--20 min | +| Prerequisites (Amazon OpenSearch Serverless NextGen collection, collection group, policies, IAM, VPC peering) | 15--20 min | | Step 3: Deploy Migration Assistant (CloudFormation + Helm) | 15--25 min | | Steps 4--9: Configure and test connectivity | 5--10 min | | Step 10: Pilot migration (small index) | 15--20 min | @@ -111,9 +111,9 @@ Expected output: ### Target collection requirements -The target OpenSearch Serverless collection must be configured as follows: +The target Amazon OpenSearch Serverless NextGen collection must be configured as follows: -- **Type** -- `VECTORSEARCH` for this playbook. For other workloads, use `SEARCH` or `TIMESERIES`. +- **Type** -- `VECTORSEARCH` for this playbook. For other workloads, use `SEARCH`. `TIMESERIES` is not supported on NextGen at launch (available with Classic). - **Encryption policy** -- At least one encryption policy covering the collection. - **Network policy** -- Public or VPC access depending on your requirements. - **Data access policy** -- Grants the Migration Assistant IAM role full index read and write access. @@ -224,7 +224,20 @@ aws opensearchserverless create-access-policy \ ``` {% include copy.html %} -### Step 4: Create the collection +### Step 4: Create the collection group + +NextGen collections must belong to a collection group. To create one, run the following command: + +```bash +aws opensearchserverless create-collection-group \ + --region us-east-2 \ + --name vector-search-group \ + --generation NEXTGEN \ + --standby-replicas ENABLED +``` +{% include copy.html %} + +### Step 5: Create the collection To create the collection, run the following command: @@ -232,7 +245,8 @@ To create the collection, run the following command: aws opensearchserverless create-collection \ --region us-east-2 \ --name my-target-collection \ - --type VECTORSEARCH + --type VECTORSEARCH \ + --collection-group-name vector-search-group ``` {% include copy.html %} @@ -250,10 +264,10 @@ watch -n 10 "aws opensearchserverless batch-get-collection \ When `Status` shows `ACTIVE`, record the endpoint. The following example shows the expected output for this playbook: ``` -https://3nbrhts7rv9jxatilz9e.us-east-2.aoss.amazonaws.com +https://3nbrhts7rv9jxatilz9e.aoss.us-east-2.on.aws ``` -### Step 5: Verify that you can reach the collection +### Step 6: Verify that you can reach the collection If you do not have `awscurl` installed, install it by running the following command: @@ -266,7 +280,7 @@ To verify that you can reach the collection, run the following command: ```bash awscurl --service aoss --region us-east-2 \ - "https://3nbrhts7rv9jxatilz9e.us-east-2.aoss.amazonaws.com/" + "https://3nbrhts7rv9jxatilz9e.aoss.us-east-2.on.aws/" ``` {% include copy.html %} @@ -285,7 +299,7 @@ For a planned downtime migration, follow these steps: 3. Migrate metadata. 4. Backfill documents. 5. Validate the target. -6. Point clients to the Serverless collection endpoint. +6. Point clients to the Serverless NextGen collection endpoint. If you are unsure which approach to select, use planned downtime because it involves fewer components and lower risk. {: .note } @@ -301,7 +315,7 @@ For a zero-downtime migration, follow these steps: 5. Backfill documents. 6. Replay captured traffic until the target catches up. 7. Validate the target. -8. Switch clients to the Serverless collection endpoint. +8. Switch clients to the Serverless NextGen collection endpoint. If you choose this option, your clients must send **explicit document IDs** for index and update operations. If your application depends on autogenerated IDs, do not use Capture and Replay. {: .warning } @@ -427,9 +441,9 @@ The default Amazon Simple Storage Service (Amazon S3) bucket is `s3://migrations After deployment, grant the Migration Assistant IAM role access to both the source and target by completing the following steps. -### Step 1: Update the OpenSearch Serverless data access policy +### Step 1: Update the Amazon OpenSearch Serverless NextGen data access policy -After deploying Migration Assistant, add the `migrations-role` and `snapshot-role` to the OpenSearch Serverless data access policy: +After deploying Migration Assistant, add the `migrations-role` and `snapshot-role` to the Amazon OpenSearch Serverless NextGen data access policy: ```bash # Get the current policy version @@ -539,7 +553,7 @@ aws ec2 authorize-security-group-ingress \ ``` {% include copy.html %} -The target is an OpenSearch Serverless collection with public network access, so no security group rule is needed for the target. If you configured VPC access for the collection, add an inbound rule to the collection's VPC endpoint security group as well. +The target is an Amazon OpenSearch Serverless NextGen collection with public network access, so no security group rule is needed for the target. If you configured VPC access for the collection, add an inbound rule to the collection's VPC endpoint security group as well. {: .note } @@ -642,7 +656,7 @@ Replace the workflow configuration file contents with the following configuratio }, "targetClusters": { "target": { - "endpoint": "https://3nbrhts7rv9jxatilz9e.us-east-2.aoss.amazonaws.com", + "endpoint": "https://3nbrhts7rv9jxatilz9e.aoss.us-east-2.on.aws", "allowInsecure": false, "authConfig": { "sigv4": { @@ -677,7 +691,7 @@ Replace the workflow configuration file contents with the following configuratio The following are key differences from domain-to-domain migrations: - **Source** uses `sigv4` with `service: "es"`: Amazon OpenSearch Service uses IAM authentication rather than basic authentication. -- **Target** uses `sigv4` with `service: "aoss"`: OpenSearch Serverless requires the `aoss` service name for AWS Signature Version 4 signing. +- **Target** uses `sigv4` with `service: "aoss"`: Amazon OpenSearch Serverless NextGen requires the `aoss` service name for AWS Signature Version 4 signing. - **`s3RoleArn`** is required: Amazon OpenSearch Service needs an IAM role to write snapshots to Amazon S3 (unlike self-managed Elasticsearch which uses keystore credentials). - **No `multiTypeBehavior`**: Elasticsearch 7.10 already uses single-type indexes, so no type mapping transformation is needed. @@ -707,7 +721,7 @@ If the source returns a connection timeout, verify the following: If the target returns 403, verify the following: -1. The OpenSearch Serverless data access policy includes the Migration Assistant migrations role. +1. The Amazon OpenSearch Serverless NextGen data access policy includes the Migration Assistant migrations role. 2. The network policy allows access from the Migration Assistant pods. To test connectivity manually, run the following commands: @@ -824,8 +838,8 @@ For a planned downtime migration, follow these steps: ``` {% include copy.html %} -5. Review components that Migration Assistant does not migrate (ISM or ILM policies, ingest pipelines, dashboards, cluster settings). OpenSearch Serverless does not support these features. Determine whether your workload requires alternatives before proceeding. -6. Point clients to the Serverless collection endpoint: `https://3nbrhts7rv9jxatilz9e.us-east-2.aoss.amazonaws.com`. +5. Review components that Migration Assistant does not migrate (ISM or ILM policies, ingest pipelines, dashboards, cluster settings). Amazon OpenSearch Serverless NextGen does not support these features. Determine whether your workload requires alternatives before proceeding. +6. Point clients to the Serverless NextGen collection endpoint: `https://3nbrhts7rv9jxatilz9e.aoss.us-east-2.on.aws`. 7. Update client authentication from basic authentication or IAM AWS Signature Version 4 with `service: es` to IAM AWS Signature Version 4 with `service: aoss`. ### Zero-downtime path @@ -957,10 +971,10 @@ When the replay is complete, document counts on the target should match the sour #### Step 7: Switch traffic to the target -When replay is complete and validation confirms the target is correct, switch your application clients from the capture proxy to the Serverless collection endpoint directly: +When replay is complete and validation confirms the target is correct, switch your application clients from the capture proxy to the Serverless NextGen collection endpoint directly: ``` -https://3nbrhts7rv9jxatilz9e.us-east-2.aoss.amazonaws.com +https://3nbrhts7rv9jxatilz9e.aoss.us-east-2.on.aws ``` Update your client's AWS Signature Version 4 signing from `service: es` to `service: aoss`. @@ -975,7 +989,7 @@ Do not delete the source domain immediately after cutover. Keep it available for Before removing Migration Assistant, confirm all of the following: -1. All client traffic is pointing directly at the Serverless collection and no longer at the capture proxy. +1. All client traffic is pointing directly at the Serverless NextGen collection and no longer at the capture proxy. 2. The capture proxy and Replayer are no longer needed. 3. You have kept the source domain available as a fallback for at least 24--72 hours. 4. The target collection is healthy and application error rates are normal. @@ -1004,7 +1018,7 @@ aws cloudformation wait stack-delete-complete --region us-east-2 --stack-name MA ``` {% include copy.html %} -This deletes the Amazon EKS cluster, Amazon ECR repository, IAM roles, and VPC endpoints created by Migration Assistant. It does **not** delete the source domain, the Serverless collection, or the Amazon S3 snapshot bucket. +This deletes the Amazon EKS cluster, Amazon ECR repository, IAM roles, and VPC endpoints created by Migration Assistant. It does **not** delete the source domain, the Serverless NextGen collection, or the Amazon S3 snapshot bucket. ### Step 3 (Optional): Delete the snapshot bucket @@ -1015,7 +1029,7 @@ aws s3 rb s3://migrations-default-111122223333-dev-us-east-2 --force ``` {% include copy.html %} -### Step 4 (Optional): Delete the OpenSearch Serverless collection +### Step 4 (Optional): Delete the Amazon OpenSearch Serverless NextGen collection If you created the collection for testing and no longer need it, run the following command: @@ -1125,7 +1139,7 @@ The following are common issues and their resolutions. ### Target returns 403 forbidden -The Migration Assistant IAM role is not included in the OpenSearch Serverless data access policy. Update the policy: +The Migration Assistant IAM role is not included in the Amazon OpenSearch Serverless NextGen data access policy. Update the policy: ```bash POLICY_VERSION=$(aws opensearchserverless get-access-policy \ @@ -1224,13 +1238,13 @@ workflow submit ``` {% include copy.html %} -### OpenSearch Serverless errors +### Amazon OpenSearch Serverless NextGen errors -The following errors are specific to OpenSearch Serverless targets. +The following errors are specific to Amazon OpenSearch Serverless NextGen targets. #### Index not found exception on the target -OpenSearch Serverless does not support the `_cluster/settings` API or automatic index creation through templates in the same way as Amazon OpenSearch Service. Verify that metadata migration completed successfully before backfill: +Amazon OpenSearch Serverless NextGen does not support the `_cluster/settings` API or automatic index creation through templates in the same way as Amazon OpenSearch Service. Verify that metadata migration completed successfully before backfill: ```bash console clusters curl target /_cat/indices?v @@ -1239,11 +1253,11 @@ console clusters curl target /_cat/indices?v #### Security exception with a permissions error -The OpenSearch Serverless data access policy is missing permissions. Ensure that the policy includes both collection- and index-level permissions for the Migration Assistant role. +The Amazon OpenSearch Serverless NextGen data access policy is missing permissions. Ensure that the policy includes both collection- and index-level permissions for the Migration Assistant role. #### Bulk indexing returns 413: Request too large -OpenSearch Serverless has a 10-MB request payload limit. If your documents are large, reduce the bulk batch size in the workflow configuration: +Amazon OpenSearch Serverless NextGen has a 10-MB request payload limit. If your documents are large, reduce the bulk batch size in the workflow configuration: ```json "documentBackfillConfig": { @@ -1260,7 +1274,7 @@ OpenSearch Serverless has a 10-MB request payload limit. If your documents are l For more information, see the following resources: - [Is Migration Assistant right for you?]({{site.url}}{{site.baseurl}}/migration-assistant/is-migration-assistant-right-for-you/) -- [Migrate to OpenSearch Serverless]({{site.url}}{{site.baseurl}}/migration-assistant/amazon-opensearch-serverless/) +- [Migrate to OpenSearch Serverless NextGen]({{site.url}}{{site.baseurl}}/migration-assistant/amazon-opensearch-serverless/) - [Deploying to EKS]({{site.url}}{{site.baseurl}}/migration-assistant/migration-phases/deploy/deploying-to-eks/) - [Using the Workflow CLI]({{site.url}}{{site.baseurl}}/migration-assistant/workflow-cli/getting-started/) - [Backfill]({{site.url}}{{site.baseurl}}/migration-assistant/migration-phases/backfill/) diff --git a/_migration-assistant/playbook-solr-8.11-to-opensearch-3.md b/_migration-assistant/playbook-solr-8.11-to-opensearch-3.md index 34eb1021877..2a4cde15bf8 100644 --- a/_migration-assistant/playbook-solr-8.11-to-opensearch-3.md +++ b/_migration-assistant/playbook-solr-8.11-to-opensearch-3.md @@ -22,7 +22,7 @@ Solr migrations support **backfill only**---Capture and Replay is not supported Solr migrations differ from Elasticsearch migrations because Solr uses a different HTTP API, schema format (`schema.xml`), and query syntax. Migration Assistant uses a specialized component called SolrReader to read Solr backup data (Lucene segment files), translate `schema.xml` field types to OpenSearch mappings, and bulk-index documents. For more information, see [Solr migration overview]({{site.url}}{{site.baseurl}}/migration-assistant/solr-migration/). -If your target is Amazon OpenSearch Serverless, this playbook still applies. The only differences are the target endpoint, the `authConfig.sigv4.service` value (`aoss` instead of `es`), and a one-time data access policy configuration. For the Serverless-specific target configuration, see [Migrate to OpenSearch Serverless]({{site.url}}{{site.baseurl}}/migration-assistant/amazon-opensearch-serverless/). +If your target is Amazon OpenSearch Serverless NextGen, this playbook still applies. The differences are the target endpoint, the `authConfig.sigv4.service` value (`aoss` instead of `es`), a one-time data access policy configuration, and creating a collection group before the collection. For the Serverless NextGen target configuration, see [Migrate to OpenSearch Serverless NextGen]({{site.url}}{{site.baseurl}}/migration-assistant/amazon-opensearch-serverless/). {: .tip } ## Step 1: Create a Solr backup diff --git a/_migration-assistant/playbooks/index.md b/_migration-assistant/playbooks/index.md index cbbaf0036b1..e8c7e437f35 100644 --- a/_migration-assistant/playbooks/index.md +++ b/_migration-assistant/playbooks/index.md @@ -35,7 +35,7 @@ The following table lists the available playbooks. | Playbook | Use case | |:---------|:---------| | [Elasticsearch 6.8 to OpenSearch 3.5]({{site.url}}{{site.baseurl}}/migration-assistant/playbook-elasticsearch-6-8-to-opensearch-3/) | Self-managed Elasticsearch sources requiring metadata transformation and snapshot-based backfill | -| [Amazon OpenSearch Service to OpenSearch Serverless]({{site.url}}{{site.baseurl}}/migration-assistant/playbook-amazon-opensearch-service-to-serverless/) | Managed AWS sources targeting Serverless collections | +| [Amazon OpenSearch Service to OpenSearch Serverless NextGen]({{site.url}}{{site.baseurl}}/migration-assistant/playbook-amazon-opensearch-service-to-serverless/) | Managed AWS sources targeting Serverless NextGen collections | | [Solr 8.11 to OpenSearch 3]({{site.url}}{{site.baseurl}}/migration-assistant/playbook-solr-8.11-to-opensearch-3/) | Solr snapshot-based backfill to OpenSearch | For AWS production deployments, deploy Migration Assistant on Amazon Elastic Kubernetes Service (EKS) before following a playbook. For more information, see [Deploy on Amazon EKS]({{site.url}}{{site.baseurl}}/migration-assistant/migration-phases/deploy/deploying-to-eks/). diff --git a/_migration-assistant/solr-migration/solr-backfill-guide.md b/_migration-assistant/solr-migration/solr-backfill-guide.md index 73b478d2bca..8a415e883d3 100644 --- a/_migration-assistant/solr-migration/solr-backfill-guide.md +++ b/_migration-assistant/solr-migration/solr-backfill-guide.md @@ -244,7 +244,7 @@ The following table describes the key configuration fields. | `sourceClusters..version` | The Solr version string. Must match the format `SOLR ..`, for example, `SOLR 6.6.6`, `SOLR 7.7.3`, `SOLR 8.11.4`, or `SOLR 9.7.0`. | | `sourceClusters..snapshotInfo.repos..s3RepoPathUri` | The full Amazon S3 URI in the format `s3://bucket` or `s3://bucket/subpath`. The bucket must match `s3.bucket.name` in `solr.xml`. The subpath is passed as the `location` parameter to Solr's `BACKUP` API. | | `sourceClusters..snapshotInfo.snapshots..repoName` | The repository name. Must match the `name` attribute in `solr.xml`. | -| `targetClusters..authConfig.sigv4.service` | The AWS service identifier. Use `es` for Amazon OpenSearch Service or `aoss` for OpenSearch Serverless. | +| `targetClusters..authConfig.sigv4.service` | The AWS service identifier. Use `es` for Amazon OpenSearch Service or `aoss` for Amazon OpenSearch Serverless NextGen. | | `targetClusters..authConfig.basic.secretName` | The Kubernetes secret name containing basic authentication credentials. Use this field instead of `sigv4` when targeting a self-managed cluster. | | `perSnapshotConfig.[].metadataMigrationConfig.skipEvaluateApproval` / `skipMigrateApproval` | Bypasses the per-step approval gates without disabling all approvals globally. | | `perSnapshotConfig.[].documentBackfillConfig.podReplicas` | The number of RFS pods. Each pod processes a different shard in parallel. | diff --git a/_migration-assistant/troubleshooting.md b/_migration-assistant/troubleshooting.md index 88230024534..74a58be2303 100644 --- a/_migration-assistant/troubleshooting.md +++ b/_migration-assistant/troubleshooting.md @@ -109,7 +109,7 @@ kubectl exec -it migration-console-0 -n ma -- aws sts get-caller-identity If the target is Amazon OpenSearch Service with fine-grained access control, make sure the relevant IAM role is mapped with sufficient permissions on the domain. -Use `es` as the AWS Signature Version 4 service for Amazon OpenSearch Service domains and `aoss` for Amazon OpenSearch Serverless collections. +Use `es` as the AWS Signature Version 4 service for Amazon OpenSearch Service domains and `aoss` for Amazon OpenSearch Serverless NextGen collections. {: .note } ### Authenticate using AWS Signature Version 4 on generic Kubernetes diff --git a/_migration-assistant/workflow-cli/getting-started.md b/_migration-assistant/workflow-cli/getting-started.md index 416b9913469..4b6dbcff6ac 100644 --- a/_migration-assistant/workflow-cli/getting-started.md +++ b/_migration-assistant/workflow-cli/getting-started.md @@ -142,7 +142,7 @@ If any connectivity verification fails, resolve the connectivity or authenticati ## Step 7 (Optional): Verify AWS identity -If your source or target uses AWS Signature Version 4 authentication for Amazon OpenSearch Service or Amazon OpenSearch Serverless: +If your source or target uses AWS Signature Version 4 authentication for Amazon OpenSearch Service or Amazon OpenSearch Serverless NextGen: - On EKS, verify that pod identity is working from the console pod. - On generic Kubernetes, make sure AWS credentials exist for both the console pod and the workflow executor pods. diff --git a/_migration-assistant/workflow-cli/index.md b/_migration-assistant/workflow-cli/index.md index 1917ed85c48..2019c448dea 100644 --- a/_migration-assistant/workflow-cli/index.md +++ b/_migration-assistant/workflow-cli/index.md @@ -166,4 +166,4 @@ The CLI uses this schema automatically when editing and validating configuration | First workflow | [Using the Workflow CLI]({{site.url}}{{site.baseurl}}/migration-assistant/workflow-cli/getting-started/) | | Deployment choice | [Choose your deployment]({{site.url}}{{site.baseurl}}/migration-assistant/migration-phases/deploy/) | | Elasticsearch 6.8 to OpenSearch 3.5 | [Playbook]({{site.url}}{{site.baseurl}}/migration-assistant/playbook-elasticsearch-6-8-to-opensearch-3/) | -| Amazon OpenSearch Service to Serverless | [Playbook]({{site.url}}{{site.baseurl}}/migration-assistant/playbook-amazon-opensearch-service-to-serverless/) | +| Amazon OpenSearch Service to Serverless NextGen | [Playbook]({{site.url}}{{site.baseurl}}/migration-assistant/playbook-amazon-opensearch-service-to-serverless/) |