AWS opensearch-service documentation change
Summary
Removed JSON policy example for S3 source permissions and SQS queue access
Security assessment
The removed content was an example permissions policy for S3 integration. No evidence this change addresses a security issue - appears to be routine example removal.
Diff
diff --git a/opensearch-service/latest/developerguide/configure-client-s3.md b/opensearch-service/latest/developerguide/configure-client-s3.md index eee7f9629..1f5c5a6df 100644 --- a//opensearch-service/latest/developerguide/configure-client-s3.md +++ b//opensearch-service/latest/developerguide/configure-client-s3.md @@ -70,37 +69,0 @@ The following sample policy shows the required permissions for using S3 as a sou -JSON - - -**** - - - - { - "Version": "2012-10-17", - "Statement": [ - { - "Effect": "Allow", - "Action":[ - "s3:ListBucket", - "s3:GetBucketLocation", - "s3:GetObject" - ], - "Resource": "arn:aws:s3:::/*" - }, - { - "Effect":"Allow", - "Action":"s3:ListAllMyBuckets", - "Resource":"arn:aws:s3:::*" - }, - { - "Effect": "Allow", - "Action": [ - "sqs:DeleteMessage", - "sqs:ReceiveMessage", - "sqs:ChangeMessageVisibility" - ], - "Resource": "arn:aws:sqs:us-west-2:111122223333:MyS3EventSqsQueue" - } - ] - } - -