Canned ACLs seem to be missing in s3 client
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| txAWS |
New
|
Medium
|
Duncan McGreggor | ||
Bug Description
I couldn't find canned ACLs mentioned in the s3 code, and grep'ing the source tree didn't reveal anything.
Docs:
http://
"Amazon S3 supports a set of predefined ACLs, known as canned ACLs. Each canned ACL has a predefined a set of grantees and permissions. You specify a canned ACL in your request using the x-amz-acl request header. When Amazon S3 receives a request with a canned ACL in the request, it adds the predefined grants to the ACL of the resource. The following table lists the set of canned ACLs and the associated predefined grants."
Canned ACL Names:
* private
* public-read
* public-read-write
* authenticated-read
* bucket-owner-read
* bucket-
* log-delivery-write
"When creating an object or a bucket, you cannot specify an ACL. instead, you can specify the canned ACL."
| description: | updated |
| Changed in txaws: | |
| milestone: | none → 0.3 |
| assignee: | nobody → Duncan McGreggor (oubiwann) |
| importance: | Undecided → Medium |
| description: | updated |
| Duncan McGreggor (oubiwann) wrote | #1 |
| Duncan McGreggor (oubiwann) wrote | #2 |
After some pocking around in the doc and AWS docs, the best approach seems to be to extend the put_<bucket/