- Newest
- Most votes
- Most comments
Hi! There have been a few updates to S3 recently that could explain the behavior you're seeing.
- Ensure Block Public Access Settings are off at the account level and the bucket level.
- If the object is already stored, you may need to update the object ACL either through console or CLI (aws s3api put-object-acl --bucket <bucket-name> --key <object-key> --acl public-read.
- Optionally, you could use a bucket policy as well.
Lastly - a friendly reminder to be careful with S3 public settings and public permissions as it's recommended to have this locked down and secured unless absolutely necessary to have files public. Then, if files need to be public, be careful with adjacent buckets in the account, even folders/etc within the same bucket, and even only giving out the necessary permissions to read the object (and not describe metadata).
I have the public access settings turned off but it is still not granting access to the public. Can you explain more on the ACL settings to allow public access please?
For easy S3 file/folder sharing and collaboration with external users using advanced SSO, please check NirvaShare - https://nirvashare.com
Relevant content
- Accepted Answerasked 4 years ago
- Accepted Answerasked 2 years ago
- Accepted Answerasked a year ago
- asked 2 years ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
For easy S3 file/folder sharing and collaboration with external users using advanced SSO, please check NirvaShare - https://nirvashare.com