You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently when instantiating a BedrockEncoder we are required to set the access key id, secret key, and session token. This is awkward and not ideal for long-running services like API's as the session credentials expire.
I am requesting that the BedrockEncoder support providing a boto3 client that is created outside of the encoder. This will support automatically refreshing the credentials and match the behavior of other frameworks that use the bedrock API.
It appears that there is already a client parameter available when creating a BedrockEncoder but it isn't used.
Perhaps we could support something like the following?
Currently when instantiating a BedrockEncoder we are required to set the access key id, secret key, and session token. This is awkward and not ideal for long-running services like API's as the session credentials expire.
I am requesting that the BedrockEncoder support providing a boto3 client that is created outside of the encoder. This will support automatically refreshing the credentials and match the behavior of other frameworks that use the bedrock API.
It appears that there is already a
client
parameter available when creating a BedrockEncoder but it isn't used.Perhaps we could support something like the following?
The existing logic in the encoder would be modified to only create a new client if one is not provided:
The
access_key_id
,secret_access_key
, andregion
parameters are already optional.The text was updated successfully, but these errors were encountered: