[exporter/awskinesis] use cached credentials provider #32415
Merged
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.
Description:
Wraps the
AssumeRoleProvider
in aCachedCredentials
provider, in the case the AWS role is explicitly specified in the configuration. This prevents a role assumption from happening every API call.This was causing us to get rate limited by AWS STS since it was not caching credentials.
The previous configuration basically fulfills the scenario described in the AWS Go SDK V2 docs:
Link to tracking Issue: N/A
Testing: N/A