AWS SQS binding spec
Detailed documentation on the AWS SQS binding component
To setup AWS SQS binding create a component of type
bindings.aws.sqs. 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.sqs version: v1 metadata: - name: queueName value: items - name: region value: us-west-2 - name: accessKey value: ***************** - name: secretKey value: ***************** - name: sessionToken value: *****************
WarningThe above example uses secrets as plain strings. It is recommended to use a secret store for the secrets as described here.
Spec metadata fields
|queueName||Y||Input/Output||The SQS queue name||
|region||Y||Input/Output||The specific AWS region||
|accessKey||Y||Input/Output||The AWS Access Key to access this resource||
|secretKey||Y||Input/Output||The AWS Secret Access Key to access this resource||
|sessionToken||N||Input/Output||The AWS session token to use||
ImportantWhen 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.
This component supports both input and output binding interfaces.
This component supports output binding with the following operations:
- Basic schema for a Dapr component
- Bindings building block
- How-To: Trigger application with input binding
- How-To: Use bindings to interface with external resources
- Bindings API reference
- Authenticating to AWS
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.
Last modified July 27, 2022: Remove namespace element from component examples (#2647) (ff9de5c8)