How to properly setup vertex claude 3.7? #9541
Unanswered
ProblemFactory
asked this question in
Q&A
Replies: 2 comments
-
I figured it out. I have another model setup as
From the debug log, it seems that litellm made a failed request to us-central1 but then retried with us-east5. After I delete this us-east5 model, vertex_ai/claude-3-7-sonnet@20250219 will result in 400 as expected. |
Beta Was this translation helpful? Give feedback.
0 replies
-
@ProblemFactory That is because claude models are only available in certain regions and not in us-central. See here This can be marked as resolved. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
My GCP account has 1.5M Tokens TPM quote for claude 3.7 on us-east5, but most gemini experimental models are only available in us-central1 (calling with us-east5 credential will result in 404), so I tested around how to properly setup litellm to use us-east5 for clause 3.7 and us-central1 for other models.
However, while I was doing some tests, I found out a weird behavior of litellm. When I setup a wildcard model like this:
I can use both gemini experimental models (e.g.
vertex_ai/gemini-2.0-pro-exp-02-05
) and claude 3.7 (vertex_ai/claude-3-7-sonnet@20250219
). As I further tested, the claude 3.7 calls used my quota on us-east5.However, if I add another model like this:
This model (
vertex_ai/us-central1/claude-3-7-sonnet@20250219
) could not be used, always result in 400.Also if I set wildcard model to us-east5, the gemini experimental models will 404.
My litellm has no fallback setup, so I believe that is not the issue.
What is causing this weird behavior? Is this expected?
Beta Was this translation helpful? Give feedback.
All reactions