AWS SES binding spec

Detailed documentation on the AWS SES binding component

Component format

To setup AWS binding create a component of type bindings.aws.ses. See this guide on how to create and apply a binding configuration.

See Authenticating to AWS for information about authentication-related attributes

  1. apiVersion: dapr.io/v1alpha1
  2. kind: Component
  3. metadata:
  4. name: ses
  5. namespace: default
  6. spec:
  7. type: bindings.aws.ses
  8. version: v1
  9. metadata:
  10. - name: accessKey
  11. value: *****************
  12. - name: secretKey
  13. value: *****************
  14. - name: region
  15. value: "eu-west-1"
  16. - name: sessionToken
  17. value: mysession
  18. - name: emailFrom
  19. value: "sender@example.com"
  20. - name: emailTo
  21. value: "receiver@example.com"
  22. - name: emailCc
  23. value: "cc@example.com"
  24. - name: emailBcc
  25. value: "bcc@example.com"
  26. - name: subject
  27. value: "subject"

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

FieldRequiredBinding supportDetailsExample
regionYOutputThe specific AWS region“eu-west-1”
accessKeyYOutputThe AWS Access Key to access this resource“key”
secretKeyYOutputThe AWS Secret Access Key to access this resource“secretAccessKey”
sessionTokenNOutputThe AWS session token to use“sessionToken”
emailFromNOutputIf set, this specifies the email address of the sender. See also“me@example.com”
emailToNOutputIf set, this specifies the email address of the receiver. See also“me@example.com”
emailCcNOutputIf set, this specifies the email address to CC in. See also“me@example.com”
emailBccNOutputIf set, this specifies email address to BCC in. See also“me@example.com”
subjectNOutputIf set, this specifies the subject of the email message. See also“subject of mail”

Binding support

This component supports output binding with the following operations:

  • create

Example request

You can specify any of the following optional metadata properties with each request:

  • emailFrom
  • emailTo
  • emailCc
  • emailBcc
  • subject

When sending an email, the metadata in the configuration and in the request is combined. The combined set of metadata must contain at least the emailFrom, emailTo, emailCc, emailBcc and subject fields.

The emailTo, emailCc and emailBcc fields can contain multiple email addresses separated by a semicolon.

Example:

  1. {
  2. "operation": "create",
  3. "metadata": {
  4. "emailTo": "dapr-smtp-binding@example.net",
  5. "emailCc": "cc1@example.net",
  6. "subject": "Email subject"
  7. },
  8. "data": "Testing Dapr SMTP Binding"
  9. }

The emailTo, emailCc and emailBcc fields can contain multiple email addresses separated by a semicolon.

Last modified November 12, 2021 : Merge pull request #1949 from willtsai/az-staticwebapp-versioning (c40e456)