This is a Bug Report

Description

• What went wrong?

When attempting to use a pre-existing S3 bucket in us-east-1 via the deploymentBucket configuration option, I receive an error response “Deployment bucket is not in the same region as the lambda function”.

Debugging through the Serverless code, I observed that it is attempting to match a LocationConstraint returned from the AWS SDK to the region; however, AWS Documentation states:

When the bucket’s region is US East (N. Virginia), Amazon S3 returns an empty string for the bucket’s region

Due to this, it appears the check in configureStack.js to match the bucket’s region with the specified region fails and I receive the error message.

• What did you expect should have happened?

I should have been able to use the pre-existing bucket.

• What was the config you used?

...
provider:
  name: aws
  runtime: nodejs4.3
  stage: dev
  region: us-east-1
  deploymentBucket: my-bucket-name
...

• What stacktrace or error message from your provider did you see?

Deployment bucket is not in the same region as the lambda function

Additional Data

• _Serverless Framework Version you’re using_: 1.0.2
• _Operating System_: OSX
• _Stack Trace_:
• _Provider Error messages_:

  Serverless Error ---------------------------------------

     Deployment bucket is not in the same region as the lambda
     function.