Use unauthenticated STS client for assuming payer account role #265
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What type of PR is this?
bug
What this PR does / Why we need it?
Currently, the STS client tries to build from a default config. This causes the client to believe it should be an authenticated client, however unless someone exports AWS credential in their terminal, there won't be any credentials present. This PR removes the creation of an authenticated client as it is not needed, and instead creates a bare minimum config with only the necessary properties to create the STS client we need.
Which Jira/Github issue(s) does this PR fix?
Resolves https://issues.redhat.com/browse/OSD-19733
Pre-checks (if applicable)