-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Panic in elb.CreateLoadBalancer when AWS_REGION is not set #4367
Comments
Hi @geekifier thanks for bringing this to our attention. I have reproduced this issue and will discuss with the team. |
Hi @geekifier , This is quite an old issue. I apologize for not getting to this sooner. I dont think this will be an issue in v2, if youre still running into this in v2, please open a new issue there and I will take a look. Thanks again, |
Comments on closed issues are hard for our team to see. |
Describe the bug
Stack trace is received when using running
elb.CreateLoadBalancer
and theAWS_REGION
env var is not set. This is despite the region being set in~/.aws/credentials
, and AWS_PROFILE being set to the relevant profile's name. WhenAWS_REGION
env var is set, all is good.Expected Behavior
Provide an actual error message instead of a panic.
Current Behavior
Reproduction Steps
$ env | grep AWS AWS_PROFILE=REACTED_ROLE_NAME
unset AWS_REGION
Possible Solution
Bug does not occur if I do the following:
export AWS_REGION = us-east-1
Additional Information/Context
SDK version used
v1.40.56
Environment details (Version of Go (
go version
)? OS name and version, etc.)go1.17.8 darwin/amd64, macOS 12.3.1
The text was updated successfully, but these errors were encountered: