Core lesson 12 of 18Topic: S3: storage and access
S3 Block Public Access: four settings, policy writes and existing access
S3 Block Public Access (BPA) restricts public access. Its four settings are not interchangeable. Separate rejecting a new public grant from limiting access under an existing public grant to understand why policy writes and object reads require different checks.
Explain the four settings and why effective protection depends on all applicable organization, account, bucket and access-point controls.
Know buckets, objects and GetObject. This is a reading exercise; no real public-access protection is disabled.
Rejecting a grant and limiting access are different
A bucket policy describes access rules for a bucket and its objects. An access control list (ACL) is another permission mechanism. BPA distinguishes policy-related controls from ACL-related controls. Do not read all four as one generic “deny downloads” switch.
| Setting | Effect to inspect | Important distinction |
|---|---|---|
| BlockPublicAcls | Rejects the relevant requests that specify a public ACL | Does not delete an existing ACL |
| IgnorePublicAcls | Disregards permissions granted by public ACLs | Different from rejecting a request that sets a public ACL |
| BlockPublicPolicy | Rejects new policy writes that grant public access | Does not replace or delete an existing policy |
| RestrictPublicBuckets | Limits access when a bucket or access point has a public policy | Not merely a restriction on saving a new policy |
A blocked policy write does not settle an object read
Suppose BlockPublicPolicy rejects a proposed public bucket policy. That result concerns the new policy write. It does not establish that nobody can read an existing object or that the existing policy was removed. Examine reads under the settings that actually remain in place.
RestrictPublicBuckets limits access to a bucket or access point with a public policy to AWS service principals and authorized users within the relevant owner accounts. It is not a grant of unrestricted access to everyone in the same account.
Choose an option to see the result and explanation.
Review protection above the bucket as well
- Organization policy → Account protectionOrganization protection applies to member accounts
- Account protection → Bucket protectionUse the most restrictive applicable combination
- Organization policy
- Organization BPA policies manage the four settings together, not individually.
- Account protection
- Review applicable inherited organization controls.
- Bucket protection
- A bucket setting alone is insufficient; access-point settings also matter when applicable.
A disabled bucket setting does not necessarily remove organization or account protection. A bucket can also retain its own protection when no upper-level policy applies. Requests through an access point require reviewing that layer too.
Public-policy classification is not the business requirement
BPA classifies public access using policy content and the documented trust criteria. A broad-looking Principal alone is not a complete classifier for every complex policy. Review the required business access separately from the formal public-policy classification.
The lab models selected effects, not all BPA behavior
The policy-write exercise models three fixed BlockPublicPolicy levels. The read exercise uses an aggregated RestrictPublicBuckets flag and other bounded conditions. It is not a complete evaluator for ACLs, access points or complex public-policy classification.
Check, then explain in your own words
- Separate rejection of new grants from treatment of existing access.
- Review the effective combination of applicable control levels.
- Compare policy writes and reads separately in the lab.
Check your understanding: Do IgnorePublicAcls and BlockPublicAcls reject the same requests for the same reason?
No. Disregarding public ACL grants and rejecting public-ACL writes are different.
Identify the request or permission each setting affects rather than treating the names as synonyms.
Sources and conditions checked
The official references used in this lesson are collected here with their scope, conditions and corresponding sections. Independent expert review and live AWS comparison have not been performed.
- S3 Block Public AccessChecked:
Scope and conditionsFour controls, applicable levels and most restrictive combination
Used in this lessonRejecting a grant and limiting access are different A blocked policy write does not settle an object read Review protection above the bucket as well Public-policy classification is not the business requirement
- What is Amazon S3?Checked:
Scope and conditionsObject storage; configuration and storage class affect behavior
Used in this lessonRejecting a grant and limiting access are different Public-policy classification is not the business requirement