-
Notifications
You must be signed in to change notification settings - Fork 95
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
Added configuration parameter to support non-default STS API Endpoint. #186
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.
Under checking process.
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.
Thank you for your contribution. I have added several comments to your changes. Can you check them?
…ogether. reverted sts client to support only a region parameter.
Made the recommended changes in latest commit on this PR. |
Under checking process. Please wait a moment until merged. |
Hi Can you please review this PR and merge to master. |
Checking process has been done. We will merge this PR. Sorry for waiting. |
Added a configuration parameter to allow for the user to define a non-default STS API endpoint. This will allow users to specify regional or custom STS endpoints. Regional STS endpoint usage is required when interfacing with STS via a PrivateLink VPC endpoint.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.