AWS glue documentation change
Summary
Removed redundant S3 bucket access policy example and reformatted JSON policies with proper indentation
Security assessment
While policy formatting changes improve readability, there's no evidence of security vulnerability fixes. The removed S3 policy example ('arn:aws:s3:::/*') was overly permissive but its removal isn't explicitly tied to security guidance.
Diff
diff --git a/glue/latest/dg/column-stats-prereqs.md b/glue/latest/dg/column-stats-prereqs.md index bb160cc60..5c36e7029 100644 --- a//glue/latest/dg/column-stats-prereqs.md +++ b//glue/latest/dg/column-stats-prereqs.md @@ -37,25 +36,0 @@ In the following policies, replace account ID with a valid AWS account, and repl -JSON - - -**** - - - { - "Version": "2012-10-17", - "Statement": [ - { - "Sid": "S3BucketAccess", - "Effect": "Allow", - "Action": [ - "s3:ListBucket", - "s3:GetObject" - ], - "Resource": [ - "arn:aws:s3:::/*", - "arn:aws:s3:::" - ] - } - ] - } - - @@ -102 +76,2 @@ JSON - "Statement": [{ + "Statement": [ + { @@ -128 +103,3 @@ JSON - "kms:ViaService": ["glue.us-east-1.amazonaws.com"] + "kms:ViaService": [ + "glue.us-east-1.amazonaws.com" + ] @@ -147 +123,2 @@ JSON - "Statement": [{ + "Statement": [ + { @@ -155 +131,0 @@ JSON - }] @@ -157 +133,2 @@ JSON - + ] + }