S3.createBucket with LocationContraint: '' fails

[e-gineer]

Creating an S3 bucket while setting the LocationConstraint to an empty string fails, but should work as a valid setting for US Standard according to the documentation at:

• http://docs.aws.amazon.com/AWSJavaScriptSDK/latest/AWS/S3.html#createBucket-property
• http://docs.aws.amazon.com/AmazonS3/latest/API/RESTBucketPUT.html

The workaround is simple enough (just remove LocationConstraint when working in US Standard), but I wanted to bring this to your attention / confirm it's not just me .

Code to reproduce:

aws = require 'aws-sdk'

#
# Works, as expected, creating bucket in US Standard
#

params =
  Bucket: 'bucket-test-should-work-in-us-standard'

conn = new aws.S3
  signatureVersion: 'v4'
  s3ForcePathStyle: true

conn.createBucket params, (err, result) ->
  console.dir err
  console.dir result


#
# Fails, as expected, invalid location constraint since us-east-1 is not valid
#

params =
  Bucket: 'bucket-test-should-fail'
  CreateBucketConfiguration:
    LocationConstraint: 'us-east-1'

conn = new aws.S3
  signatureVersion: 'v4'
  s3ForcePathStyle: true

conn.createBucket params, (err, result) ->
  console.dir err
  console.dir result


#
# FAILS, UNEXPECTED.
# Accoding to http://docs.aws.amazon.com/AmazonS3/latest/API/RESTBucketPUT.html
# and http://docs.aws.amazon.com/AWSJavaScriptSDK/latest/AWS/S3.html#createBucket-property
# an empty string should be a valid location constraint for US Standard region.
#

params =
  Bucket: 'bucket-test-should-work-but-doesnt'
  CreateBucketConfiguration:
    LocationConstraint: ''

conn = new aws.S3
  signatureVersion: 'v4'
  s3ForcePathStyle: true

conn.createBucket params, (err, result) ->
  console.dir err
  console.dir result


#
# FAILS, UNEXPECTED.
# Confirming that changing the connection path style still doesn't help.
#

params =
  Bucket: 'bucket-test-should-work-but-doesnt-region'
  CreateBucketConfiguration:
    LocationConstraint: ''

conn = new aws.S3
  region: 'us-east-1'

conn.createBucket params, (err, result) ->
  console.dir err
  console.dir result

[lsegal]

I can confirm this behavior. This documentation comes from the S3 documentation for PUT Bucket. It looks like the documentation there might be incorrect, I'll follow up with the S3 team to make sure.

[e-gineer]

Thanks for the quick confirmation! I've moved forward with the workaround, so please close this issue when you consider it complete from the AWS side.

[AdityaManohar]

@e-gineer The documentation has been corrected in the Amazon S3 PUT Bucket API reference as well as the SDK documentation for createBucket().

I'm marking this as closed. Feel free to open a new issue if you have any other questions.

Thanks for reporting!

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs and link to relevant comments in this thread.