AWS Bedrock

Detailed information on the AWS Bedrock conversation component

Component format

A Dapr conversation.yaml component file has the following structure:

apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
  name: awsbedrock
spec:
  type: conversation.aws.bedrock
  metadata:
  - name: endpoint
    value: "http://localhost:4566"
  - name: model
    value: amazon.titan-text-express-v1
  - name: responseCacheTTL
    value: 10m

Spec metadata fields

FieldRequiredDetailsExample
regionNAWS region for the Bedrock service.us-east-1
endpointNAWS endpoint for the component to use and connect to emulators. Not recommended for production AWS use.http://localhost:4566
accessKeyNAWS access key for authentication. It is recommended to use a secret store for this value."AKIAIOSFODNN7EXAMPLE"
secretKeyNAWS secret key for authentication. It is recommended to use a secret store for this value."wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY"
sessionTokenNAWS session token for temporary credentials. It is recommended to use a secret store for this value."session-token-example"
modelNThe LLM to use. Defaults to Bedrock’s default provider model from Amazon.amazon.titan-text-express-v1
responseCacheTTLNA time-to-live for the in-memory response cache. When set, identical requests are served from cache until they expire.10m
assumeRoleArnNARN of the role to assume for authentication.arn:aws:iam::123456789012:role/MyRole
trustAnchorArnNARN of the trust anchor for authentication.arn:aws:rolesanywhere:us-east-1:123456789012:trust-anchor/12345678-1234-1234-1234-123456789012
trustProfileArnNARN of the trust profile for authentication.arn:aws:rolesanywhere:us-east-1:123456789012:profile/12345678-1234-1234-1234-123456789012

Authenticating AWS

Instead of using a key parameter, AWS Bedrock authenticates using Dapr’s standard method of IAM or static credentials. Learn more about authenticating with AWS.