- Newest
- Most votes
- Most comments
Hi, Bedrock is brand new (still in early preview mode). Boto3 client in Lambda runtime may be a bit behind, so still unaware of Bedrock. So, why don't you check version of Boto3 on Lambda runtime and compare with your local one. That may be the source of your problem.
Also check if you're aligned with versions on this page: https://docs.aws.amazon.com/lambda/latest/dg/lambda-runtimes.html
Obviously, using a higher version of Python will bring you a newer version of Boto3.
Best,
Didier
I'm not sure if the standard Boto3 builds have the bedrock code yet. Even if you have the same version, make sure you pulled the custom builds for your docker container. I think that is what you are seeing in implementation 2.
In implementation 1, it seems more like the credentials were in an unexpected format. (type=value_error).
Jim
I had the same problem, as the bedrock is in beta stage it is not available in recent versions of boto3. To make it work, i have followed https://github.com/aws-samples/amazon-bedrock-workshop, you will find download.sh which gets latest boto3 which supports bedrock. I did build lambda layer with the boto3 downloaded from download.sh script from above github url and used it in my lambda service which worked!!
Relevant content
- asked 2 months ago
- Accepted Answerasked 2 years ago
- AWS OFFICIALUpdated a month ago
- AWS OFFICIALUpdated 10 months ago
- AWS OFFICIALUpdated 10 days ago