We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hi Team! We are trying to use AWS Bedrock from Lambda but there is some inconsistency again and again.
Sometime the Bedrock is connected and model gets invoked. but other times in the same lambda function with the same query/input it gets timeout.
[ERROR] 2024-09-12T02:53:02.888Z fed8c773-6e8d-47e0-9f15-23258903983a Unexpected error: Connect timeout on endpoint URL: "https://bedrock-runtime.ap-south-1.amazonaws.com/model/meta.llama3-8b-instruct-v1%3A0/invoke"
[ERROR] 2024-09-12T03:00:32.202Z fed8c773-6e8d-47e0-9f15-23258903983a Unexpected error: Connect timeout on endpoint URL: "https://bedrock-runtime.us-west-2.amazonaws.com/model/amazon.titan-embed-text-v2%3A0/invoke"
We are trying to use two different models from different region.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Hi Team!
We are trying to use AWS Bedrock from Lambda but there is some inconsistency again and again.
Sometime the Bedrock is connected and model gets invoked. but other times in the same lambda function with the same query/input it gets timeout.
[ERROR] 2024-09-12T02:53:02.888Z fed8c773-6e8d-47e0-9f15-23258903983a Unexpected error: Connect timeout on endpoint URL: "https://bedrock-runtime.ap-south-1.amazonaws.com/model/meta.llama3-8b-instruct-v1%3A0/invoke"
[ERROR] 2024-09-12T03:00:32.202Z fed8c773-6e8d-47e0-9f15-23258903983a Unexpected error: Connect timeout on endpoint URL: "https://bedrock-runtime.us-west-2.amazonaws.com/model/amazon.titan-embed-text-v2%3A0/invoke"
We are trying to use two different models from different region.
The text was updated successfully, but these errors were encountered: