Add support for AWS assume_role with a session token #13919
Merged
+17
−1
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
|
stevenmanton
force-pushed
the
fix-aws-assume-role-with-token
branch
from
5b73f62 to
f5bdf3b
Compare
stevenmanton
force-pushed
the
fix-aws-assume-role-with-token
branch
from
f5bdf3b to
d955784
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Title
Bug fix: AWS assume_role takes token
Relevant issues
Fixes #13918
Pre-Submission checklist
Please complete all items before asking a LiteLLM maintainer to review your PR
tests/litellm/directory, Adding at least 1 test is a hard requirement - see detailsmake test-unitNote: All but one test passes. It looks like the failing test is an issue with a missing module, which is unrelated to my change.
Type
🐛 Bug Fix
Changes
I added support for passing in the AWS session token. I confirmed that this worked as expected in my environment and that I could successfully daisychain assumed-role sessions.