AWS AmazonS3: Reformat Block Public Access headings and notes (no content change)
Summary
Heading levels were changed (e.g. '###### Important' to 'Important', '###### Note' to 'Note', '###### Topics' to '## Topics') and blank lines separating admonition blocks from body text were removed, collapsing Note/Important callouts into the surrounding paragraphs. The substantive guidance on BlockPublicAcls, IgnorePublicAcls, BlockPublicPolicy, and RestrictPublicBuckets is unchanged.
Security assessment
The diff only alters markdown heading syntax and whitespace around existing Note/Important admonitions; no new security guidance, permission, or control is introduced, and no vulnerability or incident is referenced. The underlying Block Public Access content is merely reformatted.
Evidence
+Important
Diff
diff --git a/AmazonS3/latest/userguide/access-control-block-public-access.md b/AmazonS3/latest/userguide/access-control-block-public-access.md index e8e8cbe..19ba5ff 100644 --- a//AmazonS3/latest/userguide/access-control-block-public-access.md +++ b//AmazonS3/latest/userguide/access-control-block-public-access.md @@ -23 +23 @@ When Amazon S3 evaluates whether an operation is prohibited by a block public ac -###### Important +Important @@ -38 +38 @@ Enabling Block Public Access helps protect your resources by preventing public a -###### Note +Note @@ -49 +49 @@ Enabling Block Public Access helps protect your resources by preventing public a -###### Topics +## Topics @@ -97,15 +97,3 @@ Name | Description -When this setting is set to `TRUE`, the specified operations fail (whether made through the REST API, AWS CLI, or AWS SDKs). However, existing policies and ACLs for buckets and objects aren't modified. This setting enables you to protect against public access while allowing you to audit, refine, or otherwise alter the existing policies and ACLs for your buckets and objects. - -###### Note - -Access points don't have ACLs associated with them. If you apply this setting to an access point, it acts as a passthrough to the underlying bucket. If an access point has this setting enabled, requests made through the access point behave as though the underlying bucket has this setting enabled, regardless of whether the bucket actually has this setting enabled. -`IgnorePublicAcls` | Setting this option to `TRUE` causes Amazon S3 to ignore all public ACLs on a bucket and any objects that it contains. This setting enables you to safely block public access granted by ACLs while still allowing `PutObject` calls that include a public ACL (as opposed to `BlockPublicAcls`, which rejects `PutObject` calls that include a public ACL). Enabling this setting doesn't affect the persistence of any existing ACLs and doesn't prevent new public ACLs from being set. - -###### Note - -Access points don't have ACLs associated with them. If you apply this setting to an access point, it acts as a passthrough to the underlying bucket. If an access point has this setting enabled, requests made through the access point behave as though the underlying bucket has this setting enabled, regardless of whether the bucket actually has this setting enabled. -`BlockPublicPolicy` | Setting this option to `TRUE` for a bucket causes Amazon S3 to reject calls to `PutBucketPolicy` if the specified bucket policy allows public access. Setting this option to `TRUE` for a bucket also causes Amazon S3 to reject calls to `PutAccessPointPolicy` for all of the bucket's same-account access points if the specified policy allows public access. Setting this option to `TRUE` for an access point causes Amazon S3 to reject calls to `PutAccessPointPolicy` and `PutBucketPolicy` that are made through the access point if the specified policy (for either the access point or the underlying bucket) allows public access. You can use this setting to allow users to manage access point and bucket policies without allowing them to publicly share the bucket or the objects it contains. Enabling this setting doesn't affect existing access point or bucket policies. - -###### Important - -To use this setting effectively, we recommend that you apply it at the _account_ level. A bucket policy can allow users to alter a bucket's block public access settings. Therefore, users who have permission to change a bucket policy could insert a policy that allows them to disable the block public access settings for the bucket. If this setting is enabled for the entire account, rather than for a specific bucket, Amazon S3 blocks public policies even if a user alters the bucket policy to disable this setting. +When this setting is set to `TRUE`, the specified operations fail (whether made through the REST API, AWS CLI, or AWS SDKs). However, existing policies and ACLs for buckets and objects aren't modified. This setting enables you to protect against public access while allowing you to audit, refine, or otherwise alter the existing policies and ACLs for your buckets and objects. NoteAccess points don't have ACLs associated with them. If you apply this setting to an access point, it acts as a passthrough to the underlying bucket. If an access point has this setting enabled, requests made through the access point behave as though the underlying bucket has this setting enabled, regardless of whether the bucket actually has this setting enabled. +`IgnorePublicAcls` | Setting this option to `TRUE` causes Amazon S3 to ignore all public ACLs on a bucket and any objects that it contains. This setting enables you to safely block public access granted by ACLs while still allowing `PutObject` calls that include a public ACL (as opposed to `BlockPublicAcls`, which rejects `PutObject` calls that include a public ACL). Enabling this setting doesn't affect the persistence of any existing ACLs and doesn't prevent new public ACLs from being set. NoteAccess points don't have ACLs associated with them. If you apply this setting to an access point, it acts as a passthrough to the underlying bucket. If an access point has this setting enabled, requests made through the access point behave as though the underlying bucket has this setting enabled, regardless of whether the bucket actually has this setting enabled. +`BlockPublicPolicy` | Setting this option to `TRUE` for a bucket causes Amazon S3 to reject calls to `PutBucketPolicy` if the specified bucket policy allows public access. Setting this option to `TRUE` for a bucket also causes Amazon S3 to reject calls to `PutAccessPointPolicy` for all of the bucket's same-account access points if the specified policy allows public access. Setting this option to `TRUE` for an access point causes Amazon S3 to reject calls to `PutAccessPointPolicy` and `PutBucketPolicy` that are made through the access point if the specified policy (for either the access point or the underlying bucket) allows public access. You can use this setting to allow users to manage access point and bucket policies without allowing them to publicly share the bucket or the objects it contains. Enabling this setting doesn't affect existing access point or bucket policies. ImportantTo use this setting effectively, we recommend that you apply it at the _account_ level. A bucket policy can allow users to alter a bucket's block public access settings. Therefore, users who have permission to change a bucket policy could insert a policy that allows them to disable the block public access settings for the bucket. If this setting is enabled for the entire account, rather than for a specific bucket, Amazon S3 blocks public policies even if a user alters the bucket policy to disable this setting. @@ -114 +102 @@ To use this setting effectively, we recommend that you apply it at the _account_ -###### Important +Important @@ -133 +121 @@ To perform block public access operations on an access point, use the AWS CLI se -###### Important +Important @@ -151 +139 @@ When evaluating a bucket policy, Amazon S3 begins by assuming that the policy is -###### Note +Note @@ -169 +157 @@ Bucket policies that grant access conditioned on the `aws:SourceIp` condition ke -###### Note +Note @@ -180 +168 @@ For more information about bucket policies, see [Bucket policies for Amazon S3]( -###### Note +Note @@ -271 +259 @@ Operation | Required permissions -###### Note +Note