- Newest
- Most votes
- Most comments
Sounds like you have ACL enabled on the bucket instead of the recommended Disable ACL bucket owner owns all objects.
It could be that a file was copied in from a different AWS account and because ACLs are enabled, the account that copied the object in has an ACL set on it.
Bucket and object permissions are independent of each other. An object does not inherit the permissions from its bucket. For example, if you create a bucket and grant write access to a user, you can't access that user’s objects unless the user explicitly grants you access.
Useful page here https://docs.aws.amazon.com/AmazonS3/latest/userguide/managing-acls.html
To troubleshoot this issue, you can try the following steps:
Check Object ACL: Use the AWS Management Console or the aws s3api get-object-acl command to inspect the ACL for the specific object (zyg5cjuQ004SN). Look for any explicit deny entries that might be preventing access.
Ensure that there are no conflicting policies or explicit deny statements in the bucket policy that might be overriding the intended permissions.
If there are IAM policies attached to your user or any IAM roles that grant access to the S3 bucket, review them to ensure there are no conflicting permissions.
After doing the above checks i suggest you reach out to AWS Support for further assistance. They can help troubleshoot the permissions issue and provide guidance on resolving it
Relevant content
- Accepted Answerasked a year ago
- asked a year ago
- asked 3 years ago
- AWS OFFICIALUpdated 22 days ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
Thanks! That did the trick.