Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ObjectACL, BucketACL not quite correct behavior #906

Open
evgeniiz321 opened this issue Nov 11, 2023 · 3 comments
Open

ObjectACL, BucketACL not quite correct behavior #906

evgeniiz321 opened this issue Nov 11, 2023 · 3 comments
Labels
bug Something isn't working I4 No visible changes S4 Routine U3 Regular

Comments

@evgeniiz321
Copy link

evgeniiz321 commented Nov 11, 2023

https://docs.aws.amazon.com/AmazonS3/latest/userguide/managing-acls.html

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.
  1. Create bucket with public-read-write ACL
  2. Create object1 with public-read-write ACL
  3. Create object2 without ACL (by default, access should be allowed only by an object owner)
  4. Try to get/put obj2 from a not owner - access allowed, but should be denied

Seems to be related to #904, but this one is a more general issue.

@smallhive
Copy link
Contributor

I consider, bucket with public-read-write leads to object2 with public-read-write by default, according to the bucket rules

@roman-khimov
Copy link
Member

Yeah, that's somewhat strange and I'd expect object2 to be accessible. Is this behavior confirmed for AWS?

@roman-khimov
Copy link
Member

Similar to #904.

@roman-khimov roman-khimov removed this from the v0.31.0 milestone Jul 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working I4 No visible changes S4 Routine U3 Regular
Projects
None yet
Development

No branches or pull requests

3 participants