Menu
Amazon Simple Email Service
Developer Guide

Using Delegate Sender Notifications for Amazon SES Sending Authorization

As a delegate sender, you can set up Amazon Simple Notification Service (Amazon SNS) notifications to inform you of bounces, complaints, and deliveries. The format and content of these notifications are described in Amazon SES Notifications Through Amazon SNS. Only the identity owner has the option to receive notifications by email feedback forwarding as described in Amazon SES Notifications Through Email.

Important

As the delegate sender, bounces and complaints count toward your bounce and complaint metrics, not those of the identity owner. High bounce and complaint rates put your account at risk of being shut down, so ensure that you set up notifications and have a process in place to monitor the notifications and remove recipient addresses that have bounced or complained from your mailing list.

You will be charged standard Amazon SNS rates for bounce, complaint, and delivery notifications. For more information, see the Amazon SNS pricing page.

Setting Up an Amazon SES Cross-Account Identity Notification Configuration

Before you set up notifications, you need to know the Amazon Resource Name (ARN) of the identity that the identity owner has authorized you to use, and for which you want to configure notifications. For example, the ARN for identity user@example.com would look similar to arn:aws:ses:us-east-1:123456789012:identity/user@example.com. If the identity owner has not given you the identity's ARN, refer them to the procedure in Providing the Delegate Sender with the Identity Information.

The easiest way to configure notifications is to use the Amazon SES console. You can also use the SetIdentityNotificationTopic API operation, passing the identity's ARN as the Identity parameter.

The following procedure shows you how to set up notifications by using the Amazon SES console.

To set up Amazon SNS bounce, complaint, or delivery notifications by using the Amazon SES console

  1. Sign in to the AWS Management Console and open the Amazon SES console at https://console.aws.amazon.com/ses/.

  2. In the left navigation pane, choose Cross-Account Notifications.

  3. Choose Add Notification Config.

  4. In the Edit Notification Configuration dialog box, enter the ARN of the identity that the identity owner has authorized you to use, and for which you want to configure notifications. The identity cannot belong to the account that is currently logged in. If you want to configure notifications for your own identities, see Configuring Amazon SNS Notifications for Amazon SES.

  5. Specify the existing Amazon SNS topics that you want to use for bounces, complaints, or deliveries, or create a new Amazon SNS topic.

    Important

    The Amazon SNS topics that you use for Amazon SES notifications must be within the same AWS Region in which you are using Amazon SES.

    You can choose to publish bounce, complaint, and delivery notifications to the same Amazon SNS topic or to different Amazon SNS topics. If you want to use an Amazon SNS topic that you do not own, then the owner of that topic must configure an Amazon SNS access policy that allows your account to call the SNS:Publish action on their topic. For information about how to control access to your Amazon SNS topic through the use of IAM policies, see Managing Access to Your Amazon SNS Topics.

  6. Choose Save Config to save your notification configuration. There may be a brief delay before these changes take effect.

    After you have configured your settings, you will receive bounce, complaint, or delivery notifications for the Amazon SNS topic. These notifications follow the structure described in Amazon SNS Notification Contents for Amazon SES.

Editing an Amazon SES Cross-Account Notification Configuration

The easiest way to edit notification configurations is to use the Amazon SES console. If you want to use the Amazon SES API instead, you can use the SetIdentityNotificationTopic API operation and pass the identity's ARN as the Identity parameter.

The following procedure shows you how to edit a cross-account notification configuration by using the Amazon SES console.

To edit a cross-account notification configuration by using the Amazon SES console

  1. Sign in to the AWS Management Console and open the Amazon SES console at https://console.aws.amazon.com/ses/.

  2. In the left navigation pane, choose Cross-Account Notifications.

    The cross-account identities for which you have set up notifications are listed in the Cross-Account Notifications details pane.

  3. Choose the ARN of the identity for which you want to view the notification configuration.

  4. Edit the notification settings, and then choose Save Config.

    Note

    Setting all notifications to No SNS Topic is the equivalent of removing the identity's notification configuration entirely. In this case, the ARN of the cross-account identity is removed from the list of cross-account identity ARNs in the Amazon SES console. This does not mean that you cannot continue to send for that identity; it just means that you are no longer set up to receive bounce, complaint, or delivery notifications for it. If you want to re-enable notifications, you must repeat the notification setup procedure described in Setting Up a Notification Configuration.

Viewing Your Amazon SES Cross-Account Identity Notifications

The easiest way to view your notification configurations is to use the Amazon SES console. You can also use the GetIdentityNotificationAttributes API operation, passing the identity's ARN as the Identity parameter.

Note

The only cross-account identities displayed in the cross-account identity list are the identities for which you have configured notifications by using the procedure described in Setting Up a Notification Configuration.

To view your cross-account notification configurations by using the Amazon SES console

  1. Sign in to the AWS Management Console and open the Amazon SES console at https://console.aws.amazon.com/ses/.

  2. In the left navigation pane, choose Cross-Account Notifications.

    The cross-account identities for which you have set up notifications are listed in the Cross-Account Notifications details pane.

  3. Choose the ARN of an identity.

    The Edit Configuration Notification dialog box displays the identity's settings.

Removing an Amazon SES Cross-Account Identity Notification Configuration

The easiest way to remove a notification configuration is to use the Amazon SES console. You can also use the SetIdentityNotificationTopic API operation, passing the identity's ARN as the Identity parameter, and passing null for the SnsTopic parameter. To completely remove the notification configuration, you must perform this operation for each type of notification type (bounce, complaint, or delivery) that was set.

Note

When you remove a notification configuration, the ARN of the cross-account identity is removed from the list of cross-account identity ARNs in the Amazon SES console. This does not mean that you cannot continue to send for that identity; it just means that you are no longer set up to receive bounce, complaint, or delivery notifications for it. If you want to re-enable notifications, you need to repeat the notification setup procedure described in Setting Up a Notification Configuration.

The following procedure shows you how to remove a cross-account notification configuration by using the Amazon SES console.

To remove a cross-account notification configuration by using the Amazon SES console

  1. Sign in to the AWS Management Console and open the Amazon SES console at https://console.aws.amazon.com/ses/.

  2. In the left navigation pane, choose Cross-Account Notifications.

    The cross-account identities for which you have set up notifications are listed in the Cross-Account Notifications details pane.

  3. Choose the box to the left of the cross-identity that you want to remove, and then choose Remove.

  4. In the Remove Cross-Account Notification Config dialog box, choose Delete Notification config.

    The ARN of the cross-account identity no longer appears in the list of cross-account identity ARNs. This does not mean that you cannot send for the identity, just that you no longer have configured notifications for it.