litellm - 💡(How to fix) Fix [Feature]: Use IRSA for S3 connections [1 participants]

Official PRs (…)
ON THIS PAGE

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
BerriAI/litellm#25020Fetched 2026-04-08 02:35:02
View on GitHub
Comments
0
Participants
1
Timeline
2
Reactions
0
Author
Participants
Timeline (top)
labeled ×2
RAW_BUFFERClick to expand / collapse

Check for existing issues

  • I have searched the existing issues and checked that my issue is not a duplicate.

The Feature

The logging documentation for S3 currently specifies the use of AWS access keys for authentication. We would like to use IRSA to provide better security and easier configuration.

Motivation, pitch

IRSA provides for better security through least privilege, credential isolation and audibility.

What part of LiteLLM is this about?

Proxy

LiteLLM is hiring a founding backend engineer, are you interested in joining us and shipping to all our users?

No

extent analysis

TL;DR

Update the logging documentation for S3 to use IAM Roles for Service Accounts (IRSA) instead of AWS access keys for authentication.

Guidance

  • Investigate how to configure IRSA for the Proxy component in LiteLLM to enable least privilege access and credential isolation.
  • Review the AWS documentation on IRSA to understand the requirements for setup and integration with S3 logging.
  • Consider the security benefits of using IRSA, such as improved audibility and reduced risk of credential exposure.
  • Evaluate the potential changes needed to the logging documentation and Proxy configuration to support IRSA authentication.

Notes

The implementation details of IRSA with S3 logging are not provided, so further research and testing may be necessary to ensure a smooth integration.

Recommendation

Apply workaround: Update the logging documentation to use IRSA, as it provides better security and easier configuration compared to using AWS access keys.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING