Skip to content

Feat/cache credentials across clients #6957

New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Draft
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

cbudau
Copy link

@cbudau cbudau commented Mar 21, 2025

Issue

Issue number, if available, prefixed with "#"

Description

What does this implement/fix? Explain your changes.

Testing

How was this change tested?

Additional context

Add any other context about the PR here.

Checklist

  • If you wrote E2E tests, are they resilient to concurrent I/O?
  • If adding new public functions, did you add the @public tag and enable doc generation on the package?

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

cbudau and others added 2 commits March 3, 2025 11:58
Avoid redundant credential fetches by caching credentials globally across AWS SDK v3 clients.
@cbudau cbudau requested a review from a team as a code owner March 21, 2025 15:22
Updated global memoize and integration tests
@cbudau cbudau marked this pull request as draft March 24, 2025 13:47
Copy link
Contributor

@kuhe kuhe left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviewed on a call: needs opt-in API in case anyone is relying on precise existing behavior.

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants