AWS AmazonS3 documentation change
Summary
Added JSON formatting markers and modified example ARNs (e.g., account ID placeholders)
Security assessment
Formatting improvements and placeholder standardization. One ARN change ('123456789012' to empty) appears to be a typo fix but lacks evidence of resolving a security issue.
Diff
diff --git a/AmazonS3/latest/userguide/MultiRegionAccessPointPermissions.md b/AmazonS3/latest/userguide/MultiRegionAccessPointPermissions.md index aec25797d..53efaf2fa 100644 --- a//AmazonS3/latest/userguide/MultiRegionAccessPointPermissions.md +++ b//AmazonS3/latest/userguide/MultiRegionAccessPointPermissions.md @@ -87,0 +88,6 @@ The following example Multi-Region Access Point policy grants an IAM user access +JSON + + +**** + + @@ -190,0 +198,6 @@ The following example bucket policy grants full bucket access to a specific Mult +JSON + + +**** + + @@ -213,0 +228,6 @@ The following Multi-Region Access Point policy allows account ``123456789012`` p +JSON + + +**** + + @@ -221 +241 @@ The following Multi-Region Access Point policy allows account ``123456789012`` p - "AWS":"arn:aws:iam::123456789012:user/JohnDoe" + "AWS":"arn:aws:iam:::user/JohnDoe" @@ -238,0 +260,6 @@ The following Multi-Region Access Point policy allows account ``123456789012`` p +JSON + + +**** + + @@ -246 +273 @@ The following Multi-Region Access Point policy allows account ``123456789012`` p - "AWS": "arn:aws:iam::123456789012:user/JohnDoe" + "AWS": "arn:aws:iam:::user/JohnDoe"