How do I troubleshoot Amazon SES configuration set issues?

Resolution

Email configuration set

You must configure your email-sending method to specify the name of the configuration set in the headers of your emails.

Example configuration set email header:

X-SES-CONFIGURATION-SET: myConfigset

Note: Replace myConfigset with the name of your configuration set.

You can also assign a default configuration set to the verified identity that you use as the source email address. Then, messages that you send from the identity automatically use the assigned default configuration set.

If you use Amazon SES tenant management to send messages, then specify a configuration set to assign resources to the tenant. Or, use an identity that has a default configuration set associated with the tenant to send messages.

CloudWatch destination

If you have issues with an Amazon SES configuration set to publish metrics to Amazon CloudWatch, then verify that the value source is configured correctly:

• Message tag: The message tag is a key-value pair that contains the dimension name that CloudWatch uses to pull events. For CloudWatch to detect the events, you must specify the tags as an X-SES-MESSAGE-TAGS email header.
• Email header: With this value source, Amazon SES retrieves the dimension name and values from the email headers. You can't use the following email headers as the dimension names: Received, To, From, DKIM-Signature, CC, message-id, or Return-Path.
• Link Tag: Link tags are key-value pairs used to publish click events to CloudWatch for an email campaign that has embedded links. Verify that the link tag configured correctly in both the embedded links and the configuration set.

Amazon SNS event destination

You can set up an Amazon Simple Notification Service (Amazon SNS) event destination to publish SES events to an SNS topic. If you have issues with an Amazon SES configuration set to publish SES events to an SNS topic, then verify the following:

• The SNS topic is a Standard type topic. SES doesn't support FIFO type topics.
• The SNS topic has an endpoint subscribed to the topic, and the correct endpoint is referenced for the published events.
  Note: Endpoints might have prerequisites that must be met before event publishing can begin. For example, an Email/Email-JSON endpoint requires that you confirm the subscription before the email address can receive messages. Note the relevant requirements for each endpoint protocol type when you configure your SNS topic.
• SES has the required permissions to publish notifications to your topic.
• If your SNS topic has encryption activated and uses an AWS Key Management Service (AWS KMS) key, then check your configuration requirements. Make sure that SES has permissions on the AWS KMS key for GenerateDataKey and Decrypt.

Firehose destination

If you have issues with an Amazon SES configuration set to publish SES events to an Amazon Data Firehose, then verify the following:

• You used the correct Firehose delivery stream to publish SES events.
• The AWS Identity and Access Management (IAM) role that Amazon SES uses has permissions to publish to your Firehose delivery stream.

Amazon Pinpoint destination

If you have issues with an Amazon SES configuration set to publish SES events to Amazon Pinpoint, then check your event destination configuration. Amazon Pinpoint doesn't support Delivery delays or Subscriptions event types.

EventBridge destination

If you have issues with an Amazon EventBridge destination, then check your event destination configuration. Make sure that you create a configuration set before you add the event destination to the configuration set.

For more information, see Monitoring SES events using Amazon EventBridge.