Topic lessonTopic: S3: versions, retention, replication and cost
S3 ACLs vs bucket policies: ownership, permissions and public access
Access control lists (ACLs) and policies are different S3 access controls. New buckets default to Bucket owner enforced, with ACLs disabled. Use an internal report read by an application to separate ownership, permission and protection against public access.
Distinguish Object Ownership, identity-based policies, bucket policies, ACLs and Block Public Access; choose what to inspect without immediately relaxing public-access controls.
Know IAM principals, actions and resources, and S3 buckets and objects. The example uses an application role and a general purpose bucket in the same account. No real policy or credential is needed.
Read ownership, permission and public-access protection separately
- Ownership → Read permissionOwnership settings determine whether ACL-based grants participate.
- Read permission → Public-access protectionReview public-access restrictions alongside permission statements. This is not a network path.
- Ownership
- Bucket owner enforced gives ownership to the bucket owner and disables ACL-based access.
- Read permission
- Review the role, object permission, applicable denies and conditions.
- Public-access protection
- BPA restricts public ACLs/policies; it does not grant a new read permission to the application.
Ownership, permission and absence of public access are separate properties. Disabled ACLs do not mean nobody can read an object. Enabled BPA does not mean every internal application request is denied. Fix the principal, operation and target first.
Choose an option to see the result and explanation.
Separate the default for new buckets from an existing configuration
| Setting | ACL and ownership behavior |
|---|---|
| Bucket owner enforced | Default for new buckets; ACLs disabled, bucket owner owns objects |
| Bucket owner preferred | ACLs enabled; bucket owner owns new uploads carrying bucket-owner-full-control |
| Object writer | ACLs enabled; the uploading account owns its objects |
A default does not prove an existing bucket has that configuration. Check older integrations before changing ownership settings. With Bucket owner enforced, requests to set or update ACLs fail, while reading an ACL remains supported.
Uploads to a Bucket owner enforced bucket accept no ACL or bucket-owner-full-control. Other requested ACLs fail with AccessControlListNotSupported. Inspect the upload request before deciding to enable ACLs.
Choose an option to see the result and explanation.
Read policies by principal, action, resource and condition
| Control | What to inspect |
|---|---|
| Identity-based policy | Attached to an IAM identity such as a role; inspect its actions, resources and conditions |
| Bucket policy | Resource-based policy attached to the bucket; inspect Principal, Action, Resource and Condition |
| ACL | When enabled, grants a limited set of permissions to accounts or groups; differs from an IAM identity policy |
The example is an application role making GetObject for reports/monthly.pdf. Match permissions to the object, not just the bucket, and review explicit denies, organization/session restrictions and encryption or endpoint conditions. Do not assume both identity and resource policies always need an Allow for a same-account request; analyze cross-account access separately.
Distinguish the four BPA settings by the operation they affect
| Setting | Main distinction |
|---|---|
| BlockPublicAcls | Rejects requests that set public ACLs, including applicable writes |
| IgnorePublicAcls | Ignores public ACL grants during access evaluation |
| BlockPublicPolicy | Rejects new bucket/access-point policies classified as public |
| RestrictPublicBuckets | Restricts access to buckets/access points that have public policies |
Saving a public policy and reading an object are different operations. BlockPublicPolicy alone does not establish that a GetObject based on an existing policy is denied. Applicable account, bucket and access-point controls combine, and organization policy may govern account-level protection. A bucket-only view is incomplete.
Choose an option to see the result and explanation.
Collect the request and evidence before changing access controls
- Identify the operation: upload, ACL update, policy save or GetObject.
- Match the principal and target: role/account, key/version and request route.
- Review Object Ownership, any ACL dependency, policies, denies and BPA.
- Choose a minimal correction tied to evidence; avoid treating disabled BPA or broad principals as universal fixes.
Check, then explain in your own words
- Check the actual Object Ownership setting.
- Fix principal, action and target.
- Distinguish policy and ACL roles.
- Match each BPA setting to the affected operation.
Check your understanding: Do disabled ACLs and enabled BPA necessarily stop an internal application from reading?
No. Evaluate the concrete request against its policies and applicable restrictions.
Ownership, permissions and public-access protection have different roles. A failed read is a reason to inspect its operation and evidence, not automatically disable protection.
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.
Scope and conditionsDefault new-bucket BOE; three modes; accepted upload ACLs; ownership is not public access
Used in this lessonRead ownership, permission and public-access protection separately Separate the default for new buckets from an existing configuration
- S3 access control overviewChecked:
Scope and conditionsIdentity/resource policies and resource/owner distinction; same-account example
Used in this lessonRead ownership, permission and public-access protection separately Read policies by principal, action, resource and condition
- S3 Block Public AccessChecked:
Scope and conditionsFour controls, applicable levels and most restrictive combination
Used in this lessonRead ownership, permission and public-access protection separately Distinguish the four BPA settings by the operation they affect
- S3 ACL overviewChecked:
Scope and conditionsDisabled ACL behavior; limited grants; AuthenticatedUsers is not a company-only group
Used in this lessonSeparate the default for new buckets from an existing configuration Read policies by principal, action, resource and condition
Scope and conditionsApplicable request context, explicit versus implicit deny, identity/resource/session evaluation and service exceptions; not a universal union/intersection equation.
Used in this lessonRead policies by principal, action, resource and condition
- Cross-account policy evaluationChecked:
Scope and conditionsTrusting/trusted account evaluation; assumed-role session requests are made as a role in the target account.
Used in this lessonRead policies by principal, action, resource and condition