AWS opensearch-service documentation change
Summary
Clarified OpenSearch Serverless support for point_in_time operations in migration
Security assessment
Technical clarification about migration mechanisms with no security context. Doesn't address vulnerabilities or security features.
Diff
diff --git a/opensearch-service/latest/developerguide/creating-opensearch-service-pipeline.md b/opensearch-service/latest/developerguide/creating-opensearch-service-pipeline.md index 7f35f15c4..880fb42ee 100644 --- a//opensearch-service/latest/developerguide/creating-opensearch-service-pipeline.md +++ b//opensearch-service/latest/developerguide/creating-opensearch-service-pipeline.md @@ -121 +121 @@ After you attach the policy to the pipeline role, use the **AWSOpenSearchDataMig -OpenSearch Ingestion uses your source domain version and distribution to determine what mechanism to use for migration. Some versions support the `point_in_time` option. OpenSearch Serverless uses the `search_after` option because it doesn't support `point_in_time` or `scroll`. +OpenSearch Ingestion uses your source domain version and distribution to determine what mechanism to use for migration. Some versions support the `point_in_time` option. OpenSearch Serverless uses the `search_after` option because it doesn't support `scroll`. Note that OpenSearch Serverless does support `point_in_time` (PIT) operations; however, the pipeline uses `search_after` for compatibility across all source types.