INFRASTRUCTURE LEARNINGINFRASTRUCTURE LEARNING
インフラ大全インフラ大全IT INFRASTRUCTURE / LEARNING
Infrastructure learning guide
Find a lesson or lab/

Esc to close · Search terms stay on your device

LEARNING日本語

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.

What you will learn

Explain the four settings and why effective protection depends on all applicable organization, account, bucket and access-point controls.

Prerequisite

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.

Read the four settings by their effect
SettingEffect to inspectImportant distinction
BlockPublicAclsRejects the relevant requests that specify a public ACLDoes not delete an existing ACL
IgnorePublicAclsDisregards permissions granted by public ACLsDifferent from rejecting a request that sets a public ACL
BlockPublicPolicyRejects new policy writes that grant public accessDoes not replace or delete an existing policy
RestrictPublicBucketsLimits access when a bucket or access point has a public policyNot 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.

You enable BlockPublicPolicy. Does that mean the existing bucket policy was deleted?
Read the answer and reason

Answer: No; this is a different control · BlockPublicPolicy rejects the relevant new policy writes. It does not modify the existing policy, so existing access needs a separate review.

Review protection above the bucket as well

Combine account-level and bucket-level protection
Combine account-level and bucket-level protection1: Organization policy — Organization protection applies to member accounts — Account protection. 2: Account protection — Use the most restrictive applicable combination — Bucket protection12Organization policyAccount protectionBucket protectionCombine account-level and bucket-level protection1: Organization policy — Organization protection applies to member accounts — Account protection. 2: Account protection — Use the most restrictive applicable combination — Bucket protection12OrganizationpolicyAccountprotectionBucketprotection
  1. Organization policy → Account protectionOrganization protection applies to member accounts
  2. 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

  1. Separate rejection of new grants from treatment of existing access.
  2. Review the effective combination of applicable control levels.
  3. 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.