Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BucketRegionError thrown when retreiving GetBucketPolicyDoc if account has buckets in two different regions #23

Open
madpilot opened this issue Feb 3, 2017 · 4 comments

Comments

@madpilot
Copy link

madpilot commented Feb 3, 2017

Most of our buckets live in Sydney, but we have one that lives in the US. When running iamy pull I get the following error:

Error fetching S3 data: Error listing buckets: Error while getting details for S3 bucket [redacted]: GetBucketPolicyDoc for [redacted]: BucketRegionError: incorrect region, the bucket is not in 'ap-southeast-2' region

It looks like the Go SDK can't handle multiple regions for S3 buckets.

@madpilot madpilot changed the title BucketRegionError thrown when retreiving Get if account has buckets in two different regions BucketRegionError thrown when retreiving GetBucketPolicyDoc if account has buckets in two different regions Feb 3, 2017
@sidewinder12s
Copy link

Could a flag be added to skip S3 bucket policies? I had hoped to try this out but it looks like it just errors out on region so we can't even try using it in most of our accounts.

@MukeshSingh28
Copy link

Yes, same issue with me too

@mtibben
Copy link
Member

mtibben commented Jun 23, 2017

HI @madpilot @sidewinder12s @MukeshSingh28 I can't reproduce this issue.

Can you reproduce it with the latest version of iamy?

And for any bucket with this problem, can let me know the result of aws s3api get-bucket-location and aws s3api get-policy and echo $AWS_REGION

@joffotron
Copy link

@madpilot Seems fixed for our env with iamy 2.1.1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants