-
Notifications
You must be signed in to change notification settings - Fork 265
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
Correct instantiation of AWS session object #421
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍 LGTM, thanks!
I'm good with your changes, but rather than making users specify:
|
It was purely a case of not changing existing behaviour. You can do exactly as you describe and force the regional endpoint when creating the session object; I've seen some controllers/drivers do that. If you're happy to have that slight change in behaviour then I can tweak the PR. That would be one less Kustomization patch I have to have 😉 |
Cool, I’m good with hard coding it in the session! Mind adding to this pr? |
The region needs to be set on the config object before creating the session so that things like setting `AWS_STS_REGIONAL_ENDPOINTS` can take effect. Also, if credentials cannot be acquired, die at that point instead of carrying on.
Done |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nice! Thank you! LGTM
The region needs to be set on the config object before creating the
session so that things like setting
AWS_STS_REGIONAL_ENDPOINTS
cantake effect.
Also, if credentials cannot be acquired, die at that point instead of
carrying on.
Fixes #420
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.