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).
- Accepted Answerasked 4 years ago
- Accepted Answerasked 2 years ago
- asked 2 years ago
- AWS OFFICIALUpdated 7 months ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 2 months ago
- EXPERTpublished a year ago
- EXPERTpublished 4 months ago