create persistent credentials provider #27
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.
Hello! My name is Sarah, and I'm a backend engineer at Zapier. We've been using your SQS sink connector, and we've made a few tweaks to it in our own fork. We are planning to submit a few pull requests with changes that we think would be useful to the community at large.
This PR introduces a change to the STS Assume Role auth provider. It moves the creation of the
CredentialsProvider
into theconfigure
method. The benefit to this change is that theCredentialsProvider
is only created once. ThengetCredentials
will use cached credentials until they expire, at which point therefresh
method is called.At high volumes of events, we found that creating the
CredentialsProvider
in thegetCredentials
method led to AWS rate limits. This change resolved the rate limit errors for us.