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).
A lambda function to delete old archive files in s3 bucketasked 3 years ago
New s3 bucket, filling with files before anything was connectedAccepted Answerasked 6 months ago
Sharing file with URL link in S3asked 8 months ago
Help with S3 redirectAccepted Answerasked 5 months ago
How do I share Amazon S3 files with users who don't have AWS Management Console access?Accepted Answerasked 2 years ago
Where can I found the uri of my Bucket to connect my Symfony application with S3 and upload files?asked 5 months ago
Private S3 bucket and http referer policy for a Wordpress site not workingasked 2 years ago
Changing S3 Bucket Region of Aws Amplifyasked a month ago
move multiple files from source S3 bucket into target S3 with source File Namesasked 11 days ago
How to delete old files deployed in S3 with CodePipelineasked 3 months ago