-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
aws s3 cp/sync and canned ACLs #663
Comments
asieira
added a commit
to asieira/aws-cli
that referenced
this issue
Feb 21, 2014
Adding all canned ACL names as documented in http://docs.aws.amazon.com/AmazonS3/latest/dev/ACLOverview.html#CannedAC L.
jamesls
added a commit
that referenced
this issue
Feb 21, 2014
* asieira-develop: Adding support for all S3 canned ACLs (#663)
jamesls
added a commit
that referenced
this issue
Feb 21, 2014
Closed via #664 |
jamesls
added a commit
that referenced
this issue
Feb 28, 2014
* release-1.3.0: (44 commits) Bumping version to 1.3.0 Fix autocomplete test Initial commit of datapipeline port Don't run Ctrl+C test on windows Don't remove paging params from arg table, hide them Remove dateutil as a dep, not needed Add stable priority queue for task queue Add ability to immediately shutdown executor Add changlog entry for deadlock bug Fix race condition in CreateLocalFileTask Fix failing unittests Use only QUEUE_END_SENTINEL for triggering shutdowns Fix hanging Ctrl+C on S3 downloads compare s3's last modified time using server's timezone Update changelog entry for #663 Adding support for all S3 canned ACLs (#663) Update CHANGELOG with latest bug fixes Fix failing completer test Add note about configure being used to set preview services A better fix for pagination. ...
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Looking at the aws s3 cp/sync documentation I see the following limitation for ACLs:
I think it would really be helpful if full support of all the canned ACLs as listed here was added.
In particular, I am having a hard time replicating the behavior of
bucket-owner-full-control
when accessing a bucket using credentials from a different AWS account than the bucket.The text was updated successfully, but these errors were encountered: