AWS opensearch-service documentation change
Summary
Restructured the collection creation steps: moved 'Serverless generation' selection earlier, adjusted step numbering, and maintained the same security settings (Standard create, Public access, custom access policy).
Security assessment
No security vulnerabilities are addressed. Changes are procedural (step reordering) without modifying security configurations or policies. Security settings like access policies remain unchanged.
Diff
diff --git a/opensearch-service/latest/developerguide/osis-serverless-get-started.md b/opensearch-service/latest/developerguide/osis-serverless-get-started.md index 5409b58ba..44ba56557 100644 --- a//opensearch-service/latest/developerguide/osis-serverless-get-started.md +++ b//opensearch-service/latest/developerguide/osis-serverless-get-started.md @@ -84 +84 @@ First, create a collection to ingest data into. We'll name the collection `inges - 3. Name the collection **ingestion-collection**. + 3. In the **Serverless generation** field, choose **Switch to Classic**. @@ -86 +86 @@ First, create a collection to ingest data into. We'll name the collection `inges - 4. For **Security** , choose **Standard create**. + 4. Name the collection **ingestion-collection**. @@ -88 +88 @@ First, create a collection to ingest data into. We'll name the collection `inges - 5. Under **Network access settings** , change the access type to **Public**. + 5. For **Security** , choose **Standard create**. @@ -90 +90 @@ First, create a collection to ingest data into. We'll name the collection `inges - 6. Keep all other settings as their defaults and choose **Next**. + 6. Under **Network access settings** , change the access type to **Public**. @@ -92 +92 @@ First, create a collection to ingest data into. We'll name the collection `inges - 7. Now, configure a data acces policy for the collection. Deselect **Automatically match access policy settings**. + 7. Keep all other settings as their defaults and choose **Next**. @@ -94 +94,3 @@ First, create a collection to ingest data into. We'll name the collection `inges - 8. For **Definition method** , choose **JSON** and paste the following policy into the editor. This policy does two things: + 8. Now, configure a data acces policy for the collection. Deselect **Automatically match access policy settings**. + + 9. For **Definition method** , choose **JSON** and paste the following policy into the editor. This policy does two things: @@ -125 +127 @@ First, create a collection to ingest data into. We'll name the collection `inges - 9. Modify the `Principal` elements to include your AWS account ID. For the second principal, specify a user or role that you can use to query the collection later. + 10. Modify the `Principal` elements to include your AWS account ID. For the second principal, specify a user or role that you can use to query the collection later. @@ -127 +129 @@ First, create a collection to ingest data into. We'll name the collection `inges - 10. Choose **Next**. Name the access policy **pipeline-collection-access** and choose **Next** again. + 11. Choose **Next**. Name the access policy **pipeline-collection-access** and choose **Next** again. @@ -129 +131 @@ First, create a collection to ingest data into. We'll name the collection `inges - 11. Review your collection configuration and choose **Submit**. + 12. Review your collection configuration and choose **Submit**.