8 views
-/https://github.com/berriai/litellm/issues/27612
GitHub · issue

#27612 [Bug]: Regional inference profile prefix stripped when storing Bedrock model, causing wrong-region prices in UI

  • State: open
  • Author: @minialexd
  • Labels: bug, llm translation, ui-dashboard

### Check for existing issues

- [x] I have searched the existing issues and checked that my issue is not a duplicate.

### What happened?

Adding an AWS Bedrock regional inference profile via the UI (e.g. bedrock/au.anthropic.claude-sonnet-4-5-20250929-v1:0) strips the au. prefix when storing the model. LiteLLM then auto-populates pricing from the us-east-1 registry entry instead of the regional one. Billing is correct (request-time lookup uses the full regional key), but the UI and the cost_breakdown.cache_creation_cost field show wrong-region values.

<img width="2724" height="1142" alt="Image" src="https://github.com/user-attachments/assets/439597a3-f6eb-43e0-811a-9b8cf9adf631" />

### Steps to Reproduce

1. Add a model with litellm_model = bedrock/au.anthropic.claude-sonnet-4-5-20250929-v1:0. Don't enter manual prices. 2. Check the stored record and the model detail page.

**Stored record (note the stripped key):** { "key": "anthropic.claude-sonnet-4-5-20250929-v1:0", "input_cost_per_token": 0.000003, "output_cost_per_token": 0.000015, "cache_creation_input_token_cost": 0.00000375 } **model_map_value resolved at request time (correct):** { "key": "au.anthropic.claude…

GitHub resolver

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

Refresh page
vote history (3 events)
#0 of 0 · 31d19h2m31s ago — entered · #import:https:::github.com:berriai:litellm post #1921
The right-hand issue is harder because it requires provider-specific request translation, validation against AWS Converse behavior, and regression coverage across caching variants. The left-hand issue is comparatively localized to model-key preservation and pricing metadata propagation in the UI path.
Streaming cost reporting spans response assembly, SSE protocol semantics, provider compatibility, and end-to-end accounting tests, creating broader integration and backward-compatibility risk. The regional model-key defect is more localized to persistence, pricing lookup, and dashboard handling.
#0 of 0 · 31d18h27m20s ago — current · #import:https:::github.com:berriai:litellm post #2492
The left issue is harder because it crosses request-type handling, spend-log serialization, configuration propagation, persistence behavior, and regression coverage. The right issue is more localized to model-key normalization and the associated pricing/UI path.
discussed in #import:https:::github.com:berriai:litellm

ranked child groups

no voted pairs yet in this scope

cli
src
spread
search