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

us-east-1 S3 is a special case #2

Closed
brianr2600 opened this issue Aug 22, 2024 · 1 comment · Fixed by #6
Closed

us-east-1 S3 is a special case #2

brianr2600 opened this issue Aug 22, 2024 · 1 comment · Fixed by #6
Assignees

Comments

@brianr2600
Copy link
Contributor

To create buckets in us-east-1, you must omit the LocationConstraint field as specifying us-east-1 there produces an error. See https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateBucketConfiguration.html#API_CreateBucketConfiguration_Contents

Simply putting the bucket in another region doesn't seem to help - the S3 client hits the wrong endpoint and gets stuck in a redirect loop. As a workaround, I removed CreateBucketConfiguration from interna/aws/aws.go. As expected it breaks every region except us-east-1, so a proper patch is still needed.

@kkb0318 kkb0318 self-assigned this Aug 23, 2024
kkb0318 added a commit that referenced this issue Aug 25, 2024
@kkb0318 kkb0318 linked a pull request Aug 25, 2024 that will close this issue
kkb0318 added a commit that referenced this issue Aug 25, 2024
@kkb0318
Copy link
Owner

kkb0318 commented Aug 25, 2024

@brianr2600

Thank you for creating the issue!

I have resolved it with #6.

I plan to release the fix along with the resolution for issue #2 in version 0.3.1. Please stay tuned for the upcoming release.

Version 0.3.1 has been released.

brianr2600 pushed a commit to brianr2600/irsa-manager that referenced this issue Sep 11, 2024
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

Successfully merging a pull request may close this issue.

2 participants