AWS AmazonS3 documentation change
Summary
Added JSON formatting blocks and modified resource ARN pattern in policy example
Security assessment
Formatting changes improve documentation structure. ARN modification from 'amzn-s3-demo-bucket1/Jane/*' to '/Jane/*' appears to be a documentation example correction rather than a security fix
Diff
diff --git a/AmazonS3/latest/userguide/access-points-policies.md b/AmazonS3/latest/userguide/access-points-policies.md index 5eceb144a..1446b5b72 100644 --- a//AmazonS3/latest/userguide/access-points-policies.md +++ b//AmazonS3/latest/userguide/access-points-policies.md @@ -37,0 +38,6 @@ The following access point policy grants IAM user ``Jane`` in account ``12345678 +JSON + + +**** + + @@ -55,0 +63,6 @@ For the access point policy to effectively grant access to ``Jane``, the underly +JSON + + +**** + + @@ -66 +79 @@ For the access point policy to effectively grant access to ``Jane``, the underly - "Resource": "arn:aws:s3:::amzn-s3-demo-bucket1/Jane/*" + "Resource": "arn:aws:s3:::/Jane/*" @@ -73,0 +88,6 @@ The following access point policy grants IAM user ``Mateo`` in account ``1234567 +JSON + + +**** + + @@ -96,0 +118,6 @@ The following access point policy allows IAM user `Arnav` in the account ``12345 +JSON + + +**** + + @@ -114,0 +143,6 @@ The following service control policy requires all new access points to be create +JSON + + +**** + + @@ -138,0 +174,6 @@ Before using a statement like the one shown in this example, make sure that you +JSON + + +**** + + @@ -230,0 +273,6 @@ You can delegate access control for a bucket to the bucket's access points. The +JSON + + +**** + + @@ -253,0 +303,6 @@ Replace `Bucket ARN` with the ARN of the bucket. +JSON + + +**** + +