aws s3api create-bucket throws error for us-east-2 #2603

mickengland · 2017-05-12T18:15:49Z

aws s3api create-bucket --bucket dev-xxxx-com-state --region us-east-2

A client error (IllegalLocationConstraintException) occurred when calling the CreateBucket operation: The unspecified location constraint is incompatible for the region specific endpoint this request was sent to.

Works fine with us-east-1.

aws --version
aws-cli/1.7.45 Python/2.7.10 Darwin/16.5.0

JordonPhillips · 2017-05-12T19:30:51Z

You need to specify the location constraint for every region except us-east-1. See the docs for examples.

Alternatively, you can use mb which will handle that for you.

rramani7 · 2017-10-05T01:02:59Z

Even though I used LocationConstraint but ended up getting exceptions , checking details of parameter suggest we have finite list for location. I can use AWS web console to create bucket with region as us-east-2 but can't create bucket through awscli create-bucket even after using locationconstraint with region as us-east-2.

{
"LocationConstraint": "EU"|"eu-west-1"|"us-west-1"|"us-west-2"|"ap-south-1"|"ap-southeast-1"|"ap-southeast-2"|"ap-northeast-1"|"sa-east-1"|"cn-north-1"|"eu-central-1"
}

mb seems to be alternate method and going to try that but awscli create-bucket should fix this inconsistency.

n3ph · 2017-11-05T22:41:09Z

Bump.

Facing same problem with duplicity / boto here... (eu-central-1)
On Bucket creation attempt I get:

<Error><Code>IllegalLocationConstraintException</Code><Message>The EU location constraint is incompatible for the region specific endpoint this request was sent to.</Message><RequestId>237A164CEBB07087</RequestId><HostId>oEDaB4OT/MlUGIJ0j1GJH7ezXqldUZa2sFKRPz3iHqAZsnpOyKiRGDV69hP/FTXK1j90ogcJB/Y=</HostId></Error>

If I create the Bucket manually everything is working fine...

Please have a look at your log files...

adv4000 · 2017-12-05T04:27:54Z

I fixed it in Boto3:

os.environ['AWS_DEFAULT_REGION'] = 'eu-west-2'
myS3 = boto3.resource('s3')
results = myS3.create_bucket(
                             Bucket='zxvxdvx.gsdrgerrrczxczxcgggzxczxczxc',
                             CreateBucketConfiguration={'LocationConstraint': AWS_DEFAULT_REGION}
                            )

shahzeb1 · 2018-09-18T06:30:54Z

For those of you looking to create a bucket via the CLI, run this:

aws s3api create-bucket --bucket my-bucket-name --region us-west-2 --create-bucket-configuration LocationConstraint=us-west-2

thetomasz · 2018-10-09T14:45:14Z

Posting this here for posterity. Bucket names are GLOBALLY unique! AWS CLI will give you the IllegalLocationConstraintException if you collide with an already existing bucket and you've specified a region different than the region of the already existing bucket. If you happen to guess the correct region of the existing bucket it will give you the BucketAlreadyExists exception.

jezen · 2018-10-10T11:58:28Z

@thetomasz I can't believe my luck that you posted this 21 hours before I had exactly the same issue. Thank you so much; this was exactly my problem.

Arnold1 · 2018-10-12T16:01:54Z

the following doesnt work for me:
aws s3api create-bucket --bucket avengers-docker-eb --region us-east-1 --create-bucket-configuration LocationConstraint=us-east-1

error:
An error occurred (IllegalLocationConstraintException) when calling the CreateBucket operation: The us-east-1 location constraint is incompatible for the region specific endpoint this request was sent to.

bingtimren · 2019-01-03T04:42:17Z

@thetomasz thank you so much for your post! I wish I had first seen your post before finally figured this out myself. The message is truly confusing, even misleading.

To find out if a name is already taken and figure out which region, if it's indeed taken, the bucket is located in, look at the DNS record of the name "your-bucket-name.s3.amazonaws.com". For example:

$ dig test8765.s3.amazonaws.com

; <<>> DiG 9.11.3-1ubuntu1.3-Ubuntu <<>> test8765.s3.amazonaws.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 39766
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;test8765.s3.amazonaws.com.	IN	A

;; ANSWER SECTION:
test8765.s3.amazonaws.com. 2016	IN	CNAME	s3-us-west-2-w.amazonaws.com.
s3-us-west-2-w.amazonaws.com. 5	IN	A	52.218.216.10

;; Query time: 16 msec
;; SERVER: 127.0.0.53#53(127.0.0.53)
;; WHEN: Thu Jan 03 15:16:11 AEDT 2019
;; MSG SIZE  rcvd: 99

JosiahEarl · 2019-01-04T21:35:03Z

Well this explains why my bucket name of "testbucket" wouldn't go through ;) Thanks guys.

Schmidtbit · 2019-01-10T21:55:58Z

I had the same issue. Using aws s3 mb s3://<bucket-name> --region us-east-2 worked for me.

dlandi · 2019-05-24T18:48:28Z

I just encountered this bug, myself. Come on AWS. Fix it. If the error is a global naming collision, then say so.

venu6644 · 2019-08-27T15:07:29Z

I get this error when I do Put Bucket encryption in my lambda script. Can someone help

An error occurred (IllegalLocationConstraintException) when calling the PutBucketEncryption operation: The ap-east-1 location constraint is incompatible for the region specific endpoint this request was sent to.: ClientError

dapseen · 2019-10-14T12:53:52Z

For those of you looking to create a bucket via the CLI, run this:
aws s3api create-bucket --bucket my-bucket-name --region us-west-2 --create-bucket-configuration LocationConstraint=us-west-2

worked for me

torressam333 · 2019-10-29T14:44:36Z

For everyone trying to create the bucket in us-east-1 just change the --region us-east-2 and it created perfectly and was visible in my aws console.

knowledgeshare99 · 2020-02-27T06:27:28Z

Even its worked for me after passing """"--create-bucket-configuration LocationConstraint=us-west-2"""' parameter options

aws s3api create-bucket --bucket my-bucket-name --region us-west-2 --create-bucket-configuration LocationConstraint=us-west-2

S3 bucket creation for regions other than us-east-1 needs additional LocationConstraint configuration. However this must not be set when the region is us-east-1. Details can be found here[1] [1] aws/aws-cli#2603 Bug: Issue 13095 Change-Id: I3d4fc5a6e8ec536001aec22c8d0e36c17523bb87

because aws/aws-cli#2603 (comment)

…et configuration on mock s3 create_bucket call Summary: Fixes s3_test.py. Used to fail with ``` 2) torchx.aws.test.s3_test.S3Test: test_storage_provider_file 1) AssertionError: File "torchx/aws/test/s3_test.py", line 41, in test_storage_provider_file init_plugin(None) File "torchx/aws/s3.py", line 91, in init_plugin register_storage_provider(S3(boto3.Session())) File "torchx/runtime/storage.py", line 58, in register_storage_provider assert provider.SCHEME not in _PROVIDERS ``` because the test has side-effects when setting the global `_PROVIDERS`. Also for regions other than `us-east-1` location constraint must be set on create-bucket call. See: aws/aws-cli#2603 Reviewed By: tierex Differential Revision: D28499845 fbshipit-source-id: 6dfae7ac06930ff83bc7639cfeeef6f30ddc82ed

tbanj · 2021-06-15T01:36:29Z

@dapseen thanks your solution works for me though I had extra parameter since I want to make the bucket to be publicly readable and writeable for learning purpose then also pass profile name parameter.

aws s3api create-bucket --bucket tbanj-0332124-test-bucket --acl public-read-write --region eu-west-1 --profile cloudform-tutor --create-bucket-configuration LocationConstraint=eu-west-1

pcgeek86 · 2021-12-28T01:21:50Z

I had to add --create-bucket-configuration LocationConstraint=us-west-2 to the AWS CLI command.

Why is this necessary? Seems like a pointless parameter, poor customer experience.

kdaily · 2021-12-28T18:57:18Z

@pcgeek86, thanks for the comment. Unfortunately this command is calling the S3 API directly and this requirement comes from there - you can see the same signature in the S3 CreateBucket API documentation:

https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateBucket.html#API_CreateBucket_RequestSyntax

The AWS CLI provides the aws s3 mb, which handles this for you by getting the value set for the --region. You can see that we use the CreateBucket command to do this, and add this parameter to the request body for you here.

pcgeek86 · 2021-12-29T01:03:03Z

That's odd. The New-S3Bucket command in the AWS PowerShell module doesn't require that extra parameter. I'm pretty sure it's just calling CreateBucket under the hood. 🤷🏻‍♂️

New-S3Bucket -BucketName (New-Guid).Guid -Region us-west-2

kdaily · 2021-12-29T23:00:55Z

Looks like they have some logic to do it too, @pcgeek86!

https://github.com/aws/aws-tools-for-powershell/blob/f62685a17fde877f828e9c4b4a382bb3a9220169/modules/AWSPowerShell/Cmdlets/S3/Advanced/New-S3Bucket-Cmdlet.cs#L153-L156

AlessioCampanelli · 2022-10-09T20:47:16Z

Posting this here for posterity. Bucket names are GLOBALLY unique! AWS CLI will give you the IllegalLocationConstraintException if you collide with an already existing bucket and you've specified a region different than the region of the already existing bucket. If you happen to guess the correct region of the existing bucket it will give you the BucketAlreadyExists exception.

thanks a lot! brilliant suggestion.

JordonPhillips added api-question s3api labels May 12, 2017

JordonPhillips closed this as completed May 12, 2017

thetomasz mentioned this issue Oct 9, 2018

s3api can't handle region correctly #3044

Closed

diehlaws added guidance Question that needs advice or information. service-api This issue is due to a problem in a service API, not the SDK implementation. and removed api-question labels Jan 4, 2019

dminkley mentioned this issue Feb 1, 2019

Issue with non-default AWS regions during PlotCritic setup jbelyeu/SV-plaudit#20

Closed

justnance mentioned this issue May 2, 2019

ConstraintException s3 create bucket name to short #3723

Closed

justnance added the documentation This is a problem with documentation. label May 8, 2019

NorfairKing mentioned this issue Apr 20, 2020

Unable to create an s3 bucket in the EU NixOS/nixops-aws#88

Closed

pierrebeitz added a commit to mesosphere/dcos-docs-site that referenced this issue Oct 14, 2020

add an explicit location constraint

3401858

because aws/aws-cli#2603 (comment)

pierrebeitz added a commit to mesosphere/dcos-docs-site that referenced this issue Oct 15, 2020

add an explicit location constraint

3785a57

because aws/aws-cli#2603 (comment)

janipalsamaki mentioned this issue Apr 7, 2021

RPA.Cloud.AWS: Create Bucket: Add automatic or manual support for location constraints robocorp/rpaframework#163

Closed

grottohub mentioned this issue Jul 26, 2021

if a bucket exists in ANOTHER region, it gives a different error which isn't caught pilot-framework/pilot-examples#1

Closed

rudpot mentioned this issue Sep 15, 2021

Error in CI/CD setup aws-samples/aws-ecs-anywhere-workshop-samples#4

Open

mdedetrich mentioned this issue Oct 4, 2021

S3: Allow bucket creation besides us-east-1 for AWS akka/alpakka#2742

Merged

dutts mentioned this issue Jul 19, 2022

Compatibility with latest version of localstack polovyivan/localstack-s3-events-to-sqs#1

Merged

matej-g mentioned this issue Nov 18, 2022

AWS me-central-1 region is incompatible thanos-io/thanos#5904

Closed

sanoyo mentioned this issue Feb 18, 2023

yaml読み込んで、s3を構築できるようにする sanoyo/aws-deployer#5

Merged

arjun289 mentioned this issue Jun 8, 2023

S3 bucket creation step fails for certain regions garystafford/emr-demo#4

Open

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

aws s3api create-bucket throws error for us-east-2 #2603

aws s3api create-bucket throws error for us-east-2 #2603

mickengland commented May 12, 2017

JordonPhillips commented May 12, 2017

rramani7 commented Oct 5, 2017 •

edited

Loading

n3ph commented Nov 5, 2017 •

edited

Loading

adv4000 commented Dec 5, 2017

shahzeb1 commented Sep 18, 2018 •

edited

Loading

thetomasz commented Oct 9, 2018

jezen commented Oct 10, 2018

Arnold1 commented Oct 12, 2018

bingtimren commented Jan 3, 2019 •

edited

Loading

JosiahEarl commented Jan 4, 2019

Schmidtbit commented Jan 10, 2019

dlandi commented May 24, 2019

venu6644 commented Aug 27, 2019

dapseen commented Oct 14, 2019

torressam333 commented Oct 29, 2019

knowledgeshare99 commented Feb 27, 2020

tbanj commented Jun 15, 2021

pcgeek86 commented Dec 28, 2021

kdaily commented Dec 28, 2021

pcgeek86 commented Dec 29, 2021

kdaily commented Dec 29, 2021

AlessioCampanelli commented Oct 9, 2022

aws s3api create-bucket throws error for us-east-2 #2603

aws s3api create-bucket throws error for us-east-2 #2603

Comments

mickengland commented May 12, 2017

JordonPhillips commented May 12, 2017

rramani7 commented Oct 5, 2017 • edited Loading

n3ph commented Nov 5, 2017 • edited Loading

adv4000 commented Dec 5, 2017

shahzeb1 commented Sep 18, 2018 • edited Loading

thetomasz commented Oct 9, 2018

jezen commented Oct 10, 2018

Arnold1 commented Oct 12, 2018

bingtimren commented Jan 3, 2019 • edited Loading

JosiahEarl commented Jan 4, 2019

Schmidtbit commented Jan 10, 2019

dlandi commented May 24, 2019

venu6644 commented Aug 27, 2019

dapseen commented Oct 14, 2019

torressam333 commented Oct 29, 2019

knowledgeshare99 commented Feb 27, 2020

tbanj commented Jun 15, 2021

pcgeek86 commented Dec 28, 2021

kdaily commented Dec 28, 2021

pcgeek86 commented Dec 29, 2021

kdaily commented Dec 29, 2021

AlessioCampanelli commented Oct 9, 2022

rramani7 commented Oct 5, 2017 •

edited

Loading

n3ph commented Nov 5, 2017 •

edited

Loading

shahzeb1 commented Sep 18, 2018 •

edited

Loading

bingtimren commented Jan 3, 2019 •

edited

Loading