AWS SNS binding spec
Detailed documentation on the AWS SNS binding component
Component format
To setup AWS SNS binding create a component of type bindings.aws.sns. 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.sns
version: v1
metadata:
- name: topicArn
value: "mytopic"
- name: region
value: "us-west-2"
- name: endpoint
value: "sns.us-west-2.amazonaws.com"
- 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 |
|---|---|---|---|---|
topicArn | Y | Output | The SNS topic name | "arn:::topicarn" |
region | Y | Output | The specific AWS region | "us-east-1" |
endpoint | N | Output | The specific AWS endpoint | "sns.us-east-1.amazonaws.com" |
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