AWS_REGION environment variable doesn't work

This is a Bug Report

Description

For bug reports:

• What went wrong? I set the AWS_REGION environment variable to eu-west-1 as described in the documentation, but my API was deployed to us-east-1
• What did you expect should have happened? The API should have been deployed to the eu-west-1 AWS region
• What was the config you used? A config without a default region set
• What stacktrace or error message from your provider did you see?

For feature proposals:

• What is the use case that should be solved. The more detail you describe this in the easier it is to understand for us.
• If there is additional config how would it look

Similar or dependent issues:

• #2151

Additional Data

• Serverless Framework Version you’re using: 1.17.0
• Operating System: Windows 10 (1703)
• Stack Trace:
• Provider Error messages:

[ozbillwang]

@horike37

Here is my workaround, AWS_DEFAULT_REGION or AWS_REGION is an environment variable, it should be set like this:

provider:
  name: aws
  runtime: nodejs6.10
  region: ${env:AWS_DEFAULT_REGION, 'us-east-1'}

[jamy015]

@eahefnawy @horike37 I would think this order makes the most sense:

1. CLI option like --region=eu-west-1
2. setting in serverless.yml
3. AWS_REGION env var
4. setting in ~\.aws\config (set by the AWS CLI)
5. if nothing to setting, set us-east-1 automatically

My reasoning behind this is that more specific options should, IMO, get more precedence:

• the CLI option is the most specific because I’m telling serverless right there on the command line that I want to do that
• serverless.yml is specific to the service being deployed
• AWS_REGION is specific to serverless on the machine
• ~\.aws\config is specific to the AWS config on the machine