Region hard coded to us-east-1

[Danwakeem]

This is a Bug Report

Description

Currently we are not able to set environment variables in any region other than us-east-1 because us-east-1 is hard coded in a few places.

• What went wrong?
  I am trying to put custom environment variables outside of us-east-1

• What did you expect should have happened?
  I expected the environment variables to be set in the region specified by my environment variables.

• What was the config you used?
  I have AWS_REGION set to us-east-2

• What stacktrace or error message from your provider did you see?
  I saw my environment variables get populated in us-east-1

Proposed Solution

Remove the hard coded region config and just allow the package to inherit from the environment variable.

Additional Data

• CF explicit region
• SSM explicit region
• Account ID explicit region