Skip to content

Extend --configure so that it can perform an access check against a single bucket as opposed to 'all' buckets. #6

Merged
merged 1 commit into from Oct 12, 2011

2 participants

@mdrcode
mdrcode commented Sep 16, 2011

Previously, --configure would perform an access check by trying to list
all buckets for the account. This requires the S3 ListAllMyBuckets
permission which is typically not available to delegated IAM accounts.
With this change, --configure now accepts an (optional) bucket uri as a
parameter and if it's provided, the access check will just verify
access to that bucket individually.

i.e.

s3cmd --configure # Access Denied if the account lacks ListAllMyBuckets

But

s3cmd --configure s3://some-bucket # Still works

@mdrcode mdrcode --configure now supports per-bucket checks
Previously, --configure would perform an access check by trying to list
all buckets for the account. This requires the S3 ListAllMyBuckets
permission which is typically not available to delegated IAM accounts.
With this change, --configure now accepts an (optional) bucket uri as a
parameter and if it's provided, the access check will just verify
access to this bucket individually.

i.e.

s3cmd --configure  # Access Denied if the account lacks ListAllMyBuckets

But

s3cmd --configure s3://some-bucket # Still work
a2340ee
@mludvig mludvig merged commit a2340ee into s3tools:master Oct 12, 2011
@mludvig

Merged back to s3tools/s3cmd. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.