[C++] S3 CreateBucket fails because AWS treats us-east-1 differently than other regions

[asfimport]

When you create a bucket you must specify a locationconstraint if the region is not us-east-1.  This works if you specify a region but fails if you use the default region (and the default region has been configured to NOT be us-east-1).

When you create a bucket you must NOT specify a locationconstraint if the region is us-east-1.  This fails (Arrow specifies the locationconstraint and receives an error "InvalidLocationConstraint Message: The specified location-constraint is not valid").

CreateBucket is getting the region from options().region which is the empty string if the user didn't specify a region.

 

Reporter: Weston Pace / @westonpace
Assignee: Weston Pace / @westonpace

PRs and other links:

• GitHub Pull Request #10637

_{Note: This issue was originally created as ARROW-13228. Please see the migration documentation for further details.}

[asfimport]

Weston Pace / @westonpace:
Botocore related: boto/boto3#125

AWS related: https://docs.aws.amazon.com/cli/latest/reference/s3api/create-bucket.html

 

Notice that even the AWS command line has this quirk...

 

# Create a bucket on us-east-1
aws s3api create-bucket --bucket my-bucket --region us-east-1
# Create a bucket on us-west-2
aws s3api create-bucket --bucket my-bucket --region us-west-2 --create-bucket-configuration LocationConstraint=us-west-2

 

[asfimport]

Antoine Pitrou / @pitrou:
Issue resolved by pull request 10637
#10637