Current approach hard-coded with accessing bedrock-runtime client to use session with access_credentials. We need to handle a case where it can pick client with attached IAM role to managed service. (boto3.client)
Steps to reproduce
Simply deploy sample code using lambda function.
Attach a role to Lambda function which has access to Bedrock Invoke.
No access credentials to be generated and attached in environment, as this is unsecure approach in comparision.
Model Used
bedrock service, haiku model
Expected Behavior
Code should connect with bedrock deployed models without need to pass access credential.
Describe the bug
Current approach hard-coded with accessing bedrock-runtime client to use session with access_credentials. We need to handle a case where it can pick client with attached IAM role to managed service. (boto3.client)
Steps to reproduce
Simply deploy sample code using lambda function. Attach a role to Lambda function which has access to Bedrock Invoke. No access credentials to be generated and attached in environment, as this is unsecure approach in comparision.
Model Used
bedrock service, haiku model
Expected Behavior
Code should connect with bedrock deployed models without need to pass access credential.
Screenshots and logs
No response
Additional Information
No response