support for custom bedrock runtime endpoint #717
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…env config AWS_REGION_NAME not available
…t or .env variable AWS_BEDROCK_RUNTIME_ENDPOINT or as a parameter to init_bedrock_client
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
lgtm! sorry for the delay - bedrock issue fixed, so we can test this before merging. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Some developers are required to use specific AWS runtime endpoints (e.g., access via proxy), adding support for this:
AWS_REGIONif litellm's configurationAWS_REGION_NAMEis not setaws_bedrock_runtime_endpointas input toinit_bedrock_clientAWS_BEDROCK_RUNTIME_ENDPOINTconfig via environment variable or .env file