[
https://issues.apache.org/jira/browse/LIBCLOUD-335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13777480#comment-13777480
]
ASF subversion and git services commented on LIBCLOUD-335:
----------------------------------------------------------
Commit df3eb0179ff0c179e2433981f6917a61cf682fba in branch refs/heads/trunk from
[~johnnoone]
[ https://git-wip-us.apache.org/repos/asf?p=libcloud.git;h=df3eb01 ]
Issue LIBCLOUD-335: Add IAM Profile on node creation for ec2 based providers.
Signed-off-by: Tomaz Muraus <[email protected]>
> Storage layer is incompatible with IAM (or similar) restrictions
> ----------------------------------------------------------------
>
> Key: LIBCLOUD-335
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-335
> Project: Libcloud
> Issue Type: Bug
> Components: Storage
> Reporter: Noah Kantrowitz
> Priority: Minor
>
> If I set an IAM policy (or presumably similar for other services) that
> restricts to just operations on a single container, and then tell libcloud to
> use that container, it still tries to list all containers the provider has.
> In S3 this triggers a security error since the user doesn't have permission
> to see other buckets. This makes it difficult to restrict permissions.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
