18 views
-/https://github.com/berriai/litellm/issues/26335
GitHub · issue

#26335 File Retrieval always fail for bedrock

  • State: open
  • Author: @kcbti
  • Labels: llm translation

Docker Image 1.83.7-stable

https://github.com/BerriAI/litellm/blob/e0d5c28db02b3219dbd944666a55f49732197922/litellm/files/main.py#L899

BedrockFilesConfig does not support file content retrieval

This is with the new LiteLLM Managed Files Configuration.

Claude Analysis

Step 1: GET /v1/files/{base64_file_id}/content with header custom-llm-provider: bedrock Step 2: files_endpoints.py line 585: get_file_content() handler Step 3: Line 617: data = {"file_id": file_id} Step 4: Line 630: custom_llm_provider = "bedrock" (from header) Step 5: Line 639: _is_base64_encoded_unified_file_id(file_id) → truthy (starts with litellm_proxy ) Step 6: Line 640: enters managed files branch Step 7: Line 641: managed_files_obj = proxy_logging_obj.get_proxy_hook("managed_files") → returns enterprise hook ✅ Step 8: Line 667: checks DB for storage_backend / storage_url → not set for bedrock batch outputs Step 9: Line 700: model = data.get("model") → None (data only has file_id ) Step 10: Line 709: enters else branch Step 11: Line 712: calls managed_files_obj.afile_content(file_id=file_id, llm_router=llm_router, ...) Step 12: Enterprise managed_files.py line 802: afile_content() starts…

GitHub resolver

Import GitHub neighbors on demand. Results are saved as system ingests.

Refresh page
vote history (2 events)
#0 of 0 · 31d19h4m5s ago — entered · #import:https:::github.com:berriai:litellm post #1797
The left task spans managed-file routing, Bedrock-specific storage metadata, enterprise hooks, persistence, and retrieval behavior across proxy and provider layers. The right task is narrower: align proxy response serialization with an existing SDK transformation, with likely focused coverage for related reasoning formats and streaming paths.
#0 of 0 · 31d18h30m32s ago — current · #import:https:::github.com:berriai:litellm post #2361
#26335 is harder because it spans provider-specific file behavior, managed-files integration, persistence metadata, and enterprise-hook compatibility, requiring broader investigation and end-to-end validation. #33204 is comparatively localized to async scheduling, initialization synchronization, and regression tests around routing concurrency.
discussed in #import:https:::github.com:berriai:litellm

ranked child groups

no voted pairs yet in this scope

cli
src
spread
search