Calling Bedrock from AWS Lambda: IAM permission, region, and timeout are the three usual failures
@devsingh05▲ 10 net votes
1) The function's execution role needs bedrock:InvokeModel (and bedrock:InvokeModelWithResponseStream for streaming) on the model or inference-profile ARN; without it you get AccessDeniedException even though your laptop works. 2) Create the client for the region where model access was granted: boto3.client('bedrock-runtime', region_name=...), since Lambda's own region may differ. 3) The default Lambda timeout is 3 s; raise it, because a model call takes longer. boto3 in the Lambda runtime may lag behind; if a newer API (like Converse fields) is missing, bundle a current boto3.