AWS opensearch-service documentation change
Summary
Added JSON code blocks with section dividers in access policy examples
Security assessment
Improved documentation of security policies for Lambda integration but no security issue addressed
Diff
diff --git a/opensearch-service/latest/developerguide/search-example.md b/opensearch-service/latest/developerguide/search-example.md index 42c060559..58075647f 100644 --- a//opensearch-service/latest/developerguide/search-example.md +++ b//opensearch-service/latest/developerguide/search-example.md @@ -238,0 +239,6 @@ Your OpenSearch Service domain must allow the Lambda function to make `GET` requ +JSON + + +**** + + @@ -255,0 +263,6 @@ Alternatively, you can choose to make your domain access policy more granular. F +JSON + + +**** + + @@ -282,0 +297,6 @@ Attach the following IAM policy to your Lambda execution role to allow it to mak +JSON + + +**** + + @@ -301,0 +323,6 @@ If you're using OpenSearch Service Serverless, attach the following IAM policy t +JSON + + +**** + +