AWS vpc documentation change
Summary
Added JSON section markers and formatting dividers in multiple policy examples
Security assessment
Changes are structural formatting improvements for policy examples but do not introduce new security content or address vulnerabilities.
Diff
diff --git a/vpc/latest/privatelink/vpc-endpoints-s3.md b/vpc/latest/privatelink/vpc-endpoints-s3.md index 6ec9dfe10..92be4d03c 100644 --- a//vpc/latest/privatelink/vpc-endpoints-s3.md +++ b//vpc/latest/privatelink/vpc-endpoints-s3.md @@ -130,0 +131,6 @@ You can create a bucket policy that restricts access to a specific endpoint by u +JSON + + +**** + + @@ -154,0 +162,6 @@ You can create a bucket policy that restricts access to specific VPCs by using t +JSON + + +**** + + @@ -178,0 +193,6 @@ You can create a policy that restricts access to specific IP address ranges by u +JSON + + +**** + + @@ -202,0 +224,6 @@ You can create a policy that restricts access to the S3 buckets in a specific AW +JSON + + +**** + + @@ -278,0 +307,6 @@ You can create a policy that restricts access to specific S3 buckets only. This +JSON + + +**** + + @@ -303,0 +339,6 @@ You can create a policy that restricts access to a specific IAM role. You must u +JSON + + +**** + + @@ -326,0 +369,6 @@ You can create a policy that restricts access to a specific account. +JSON + + +**** + +