Amazon Web Services · infra · fg-0561

An S3 bucket with Block Public Access off and a public bucket policy serves your files to anyone

If you see Objects open in a browser with no signed URL or credentials, the cause and the fix for Amazon Web Services are below, last verified 2026-10-27.

Verified Oct 2026trust 50/100
Symptom
Objects open in a browser with no signed URL or credentialsThe bucket policy allows "Principal": "*" with no limiting ConditionIAM Access Analyzer for S3 lists the bucket as public
Cause
New buckets do not allow public access by default, but a bucket policy, access point policy or ACL can grant it once Block Public Access is turned off. S3 treats a policy statement for Principal "*" without a fixed-value condition as public. Block Public Access does not change existing policies, so turning it off makes a bucket with a public policy or ACL public again.
Fix
Turn on all four Block Public Access settings on the bucket, and on the account so current and future buckets are covered. If something must be public, such as a static website, keep it in its own bucket and keep user uploads in a private one.
Apply
aws s3api put-public-access-block \ --bucket my-app-uploads \ --public-access-block-configuration "BlockPublicAcls=true,IgnorePublicAcls=true,BlockPublicPolicy=true,RestrictPublicBuckets=true"
Affected
Amazon S3 buckets with Block Public Access turned off and a public bucket policy or ACL
Sources

Last verified 2026-10-27 · Confirmed by 0 builders

Related traps

Have your agent know this before it fails

$ /plugin marketplace add getfootgun/footgun
$ /plugin install footgun@footgun