You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When specifying the aws_bedrock_runtime_endpoint parameter in the proxy settings for accessing the Titan Embedding model through Bedrock, the request fails. It looks like for some reason the aws_bedrock_runtime_endpoint parameter is being passed in the request to Titan, and therefore causes a validation error because that's not a valid parameter.
I even tried using the drop_params parameter, but that did not fix the error.
Here is the config.yaml file that I used (just using the regular bedrock-runtime URL as an example of this failing, but had same issue with other values):
{"error":{"message":"litellm.BadRequestError: BedrockException - {\"message\":\"Malformed input request: extraneous key [aws_bedrock_runtime_endpoint] is not permitted, please reformat your input and try again.\"}\nReceived Model Group=titan-embedding\nAvailable Model Group Fallbacks=None","type":null,"param":null,"code":"400"}}
Are you a ML Ops Team?
No
What LiteLLM version are you on ?
v1.60.0
Twitter / LinkedIn details
No response
The text was updated successfully, but these errors were encountered:
What happened?
When specifying the aws_bedrock_runtime_endpoint parameter in the proxy settings for accessing the Titan Embedding model through Bedrock, the request fails. It looks like for some reason the aws_bedrock_runtime_endpoint parameter is being passed in the request to Titan, and therefore causes a validation error because that's not a valid parameter.
I even tried using the drop_params parameter, but that did not fix the error.
Here is the config.yaml file that I used (just using the regular bedrock-runtime URL as an example of this failing, but had same issue with other values):
Relevant log output
Are you a ML Ops Team?
No
What LiteLLM version are you on ?
v1.60.0
Twitter / LinkedIn details
No response
The text was updated successfully, but these errors were encountered: