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

Support for canned ACL bucket-owner-full-control #11697

Closed
cyberduck opened this issue Jun 4, 2021 · 3 comments
Closed

Support for canned ACL bucket-owner-full-control #11697

cyberduck opened this issue Jun 4, 2021 · 3 comments
Assignees
Labels
enhancement fixed s3 version:7.9.2
Milestone

Comments

@cyberduck
Copy link
Collaborator

@cyberduck cyberduck commented Jun 4, 2021

@dkocher created the issue

Add support for uploading objects with the bucket-owner-full-control canned ACL.

S3 Object Ownership is an Amazon S3 bucket setting that you can use to control ownership of new objects that are uploaded to your buckets. By default, when other AWS accounts upload objects to your bucket, the objects remain owned by the uploading account. With S3 Object Ownership, any new objects that are written by other accounts with the bucket-owner-full-control canned access control list (ACL) automatically become owned by the bucket owner, who then has full control of the objects.

https://docs.aws.amazon.com/AmazonS3/latest/userguide/about-object-ownership.html

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Jun 24, 2021

@dkocher commented

In 52308fa.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Jun 24, 2021

@dkocher commented

Milestone renamed

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Jul 8, 2021

@ylangisc commented

Milestone renamed

@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 27, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement fixed s3 version:7.9.2
Projects
None yet
Development

No branches or pull requests

2 participants