diff options
| -rw-r--r-- | doc/design/assistant/blog/day_92__S3/comment_2_8249d2d9521e44c674da3fda74be077a._comment | 10 |
1 files changed, 10 insertions, 0 deletions
diff --git a/doc/design/assistant/blog/day_92__S3/comment_2_8249d2d9521e44c674da3fda74be077a._comment b/doc/design/assistant/blog/day_92__S3/comment_2_8249d2d9521e44c674da3fda74be077a._comment new file mode 100644 index 000000000..fb83b23e4 --- /dev/null +++ b/doc/design/assistant/blog/day_92__S3/comment_2_8249d2d9521e44c674da3fda74be077a._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawlFd2EbAmGD0FjHmuoerXfT0GO_jPcgvQA" + nickname="Gert" + subject="Single bucket for S3" + date="2012-09-27T09:17:24Z" + content=""" +You can easily do that with IAM, checkout <http://andrewhitchcock.org/?post=325>. + +It boils down to creating a policy for each user/bucket. But allow read access to the full bucket list (otherwise the AWS Console won't work). +"""]] |