InvalidLocationConstraint error in AWS S3 handled. #1403
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Creating a bucket with the boto3 AWS S3 client may return a InvalidLocationConstraint error, if we use the default value for an AWS region ("us-east-1") in the LocationConstraint parameter. More specifically:
ClientError: An error occurred (InvalidLocationConstraint) when calling the CreateBucket operation: The specified location-constraint is not valid
This error has been previously reported:
boto/boto3#125
boto/boto3#811
I simply propose a quick fix that retries the operation without the LocationConstraint if the region is "us-east-1".
Developer's Certificate of Origin 1.1