libcloud-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (LIBCLOUD-335) Storage layer is incompatible with IAM (or similar) restrictions
Date Wed, 25 Sep 2013 13:46:10 GMT


ASF subversion and git services commented on LIBCLOUD-335:

Commit dcd1ac028af16b43959cb8a53f15a30eab920f32 in branch refs/heads/trunk from [~johnnoone]
[;h=dcd1ac0 ]

LIBCLOUD-335: EC2 IAM Profile are refactored for py2~3 and tested

Signed-off-by: Tomaz Muraus <>

> Storage layer is incompatible with IAM (or similar) restrictions
> ----------------------------------------------------------------
>                 Key: LIBCLOUD-335
>                 URL:
>             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:

View raw message