AWS DynamoDB binding spec
Detailed documentation on the AWS DynamoDB binding component
Component format
To setup AWS DynamoDB binding create a component of type bindings.aws.dynamodb. See this guide on how to create and apply a binding configuration.
See Authenticating to AWS for information about authentication-related attributes
apiVersion: dapr.io/v1alpha1 kind: Component metadata: name: <NAME> spec: type: bindings.aws.dynamodb version: v1 metadata: - name: table value: "items" - name: region value: "us-west-2" - name: accessKey value: "*****************" - name: secretKey value: "*****************" - name: sessionToken value: "*****************" Warning
The above example uses secrets as plain strings. It is recommended to use a secret store for the secrets as described here.Spec metadata fields
| Field | Required | Binding support | Details | Example |
|---|---|---|---|---|
table | Y | Output | The DynamoDB table name | "items" |
region | Y | Output | The specific AWS region the AWS DynamoDB instance is deployed in | "us-east-1" |
accessKey | Y | Output | The AWS Access Key to access this resource | "key" |
secretKey | Y | Output | The AWS Secret Access Key to access this resource | "secretAccessKey" |
sessionToken | N | Output | The AWS session token to use | "sessionToken" |
Important
When running the Dapr sidecar (daprd) with your application on EKS (AWS Kubernetes), if you’re using a node/pod that has already been attached to an IAM policy defining access to AWS resources, you must not provide AWS access-key, secret-key, and tokens in the definition of the component spec you’re using.Binding support
This component supports output binding with the following operations:
create