-
-
Notifications
You must be signed in to change notification settings - Fork 5.3k
feat: add workload identity federation between GCP and AWS #10210
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
4876edb to
e367bef
Compare
e367bef to
62bf56c
Compare
|
Here's some documentation:
Thank you! |
|
Hello @ishaan-jaff @krrishdholakia ! Is it possible to have this merged soon ? All tests have been made for the feature 🙂 Thank you! |
|
Hello guys @krrishdholakia @ishaan-jaff ! Do you have time to check this or someone of the core team? We can setup a little meeting if needed so I can show you what I tried to test this with real environment setup. Thank you! |
|
Hello again 😃 @krrishdholakia @ishaan-jaff You think guys this PR can be merged today? |
62bf56c to
04a348c
Compare
|
Hey @pascallim looks good. Can you resolve the conflicts, so we can merge this in? |
04a348c to
6201476
Compare
6201476 to
ec0afc9
Compare
|
@krrishdholakia Sorry should be fine now! 🙂 |
- Comprehensive guide for connecting AWS workloads to GCP services without service account keys - Covers EC2, EKS, and EKS Serverless (Fargate) deployments - Includes step-by-step setup, troubleshooting, and security best practices - Based on PR BerriAI#10210 for LiteLLM v1.77.x+ WIF support
Title
Allow workload identity federation between GCP and AWS
Relevant issues
Fixes #6141
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-unit)[https://docs.litellm.ai/docs/extras/contributing_code]Type
🆕 New Feature
✅ Test
Changes
Add workload identity federation between GCP and AWS. It was only done for Microsoft Azure and OIDC identity providers.