Open to refactoring bedrock interaction to use @aws-sdk/client-bedrock-runtime?

[bizob2828]

Checked

• I searched existing ideas and did not find a similar one
• I added a very descriptive title
• I've clearly described the feature request and motivation for it

Feature request

I work at New Relic on the Node.js agent team. We have instrumented langchain to get observability for customers using the library. We're getting insights into calls from openai by instrumenting the openai calls. However with AWS Bedrock, it appears that langchain is using its own implementation of bedrock. Would you be open to updating this file to rely on @aws-sdk/client-bedrock-runtime?

Motivation

At New Relic we want to avoid instrumenting similar libraries to get telemetry for interactions with AWS Bedrock. I have noticed the embeddings bit relies on @aws-sdk/client-bedrock-runtime but the LLM interactions are bespoke.

Proposal (If applicable)

Update @langchain/community/llms/bedrock to rely on @aws-sdk/client-bedrock-runtime

[danieldabate]

+1 to this request. Using the AWS SDK implementation will also enable alternative authentication methods, such as assuming IAM roles. This is mandatory in some companies that prohibit the use of static access keys.