Automatically pausing email sending for your entire Amazon SES account

To create the IAM role

1. Open the IAM console at https://console.aws.amazon.com/iam/.

2. In the navigation pane, choose Roles.

3. Choose Create role.

4. On the Select trusted entity page, choose AWS service for the Trusted entity type.

5. Under Use case, choose Lambda, then choose Next.

6. On the Add permissions page, choose the following policies:

   • AWSLambdaBasicExecutionRole

   • AmazonSESFullAccess

   Tip

   Use the search box under Permission policies to quickly locate these policies, but note that after searching for and selecting the first policy, you must choose Clear filters before searching and selecting the second policy.

   Then choose Next.

7. On the Name, review, and create page, under Role details, enter a meaningful name for the policy in the Role name field.

8. Verify that the two policies you selected are listed in the Permissions policy summary table, then choose Create role.

To create the Lambda function

1. Open the AWS Lambda console at https://console.aws.amazon.com/lambda/.

2. Use the region selector to choose the region in which you want to deploy this Lambda function.

   Note

   This function only pauses email sending in the AWS Region you select in this step. If you send email from more than one region, repeat the procedures in this section for each region in which you want to automatically pause email sending.

3. Choose Create function.

4. Under Create function, choose Author from scratch.

5. Under Basic information, complete the following steps:

   • For Function name, type a name for the Lambda function.

   • For Runtime, choose Node.js 18x (or the version currently offered in the select list).

   • For Architecture, keep the preselected default, x86_64.

   • Under Permissions, expand Change default execution role and choose Use an existing role.

   • Click inside the Existing role list box, and choose the IAM role you created in Part 1: Create an IAM Role.

   Then choose Create function.

6. Under Code source, in the code editor, paste the following code:

   'use strict';
   
   
   const { SES } = require("@aws-sdk/client-ses")
   
   // Create a new SES object. 
   
   var ses = new SES({});                  
   
   // Specify the parameters for this operation. In this case, there is only one
   // parameter to pass: the Enabled parameter, with a value of false
   // (Enabled = false disables email sending, Enabled = true enables it).
   var params = {
       Enabled: false
   };
   
   exports.handler = (event, context, callback) => {
       // Pause sending for your entire SES account
       ses.updateAccountSendingEnabled(params, function(err, data) {
           if(err) {
               console.log(err.message);
           } else {
               console.log(data);
           }
       });
   };

   Then choose Deploy.

7. Choose Test. If the Configure test event window appears, type a name in the Event name field, and then choose Save.

8. Expand the Test drop box and select the name of the event you just created, and then choose Test.

9. The Execution results tab will appear - just below it and to the right, ensure that Status: Succeeded is displayed. If the function failed to execute, do the following:

   • Verify that the IAM role you created in Part 1: Create an IAM Role contains the correct policies.

   • Verify that the code in the Lambda function does not contain any errors. The Lambda code editor automatically highlights syntax errors and other potential issues.

To re-enable email sending

1. At the command line, type the following command to re-enable email sending for your account. Replace sending_region with the name of the Region in which you want to re-enable email sending.

   aws ses update-account-sending-enabled --enabled --region sending_region

2. At the command line, type the following command to check the email sending status for your account:

   aws ses get-account-sending-enabled --region sending_region

   If you see the following output, then you have successfully re-enabled email sending for your account:

   {
       "Enabled": true 
   }

To create the Amazon SNS topic and subscribe the Lambda function to it

1. Open the Amazon SNS console at https://console.aws.amazon.com/sns/v3/home.

2. Create a topic by following the steps in the Amazon Simple Notification Service Developer Guide.

   1. The Type must be Standard (not FIFO).

3. Subscribe to the topic by following the steps in the Amazon Simple Notification Service Developer Guide.

   1. For Protocol choose AWS Lambda.

   2. For Endpoint, choose the Lambda function you created in Part 2: Create the Lambda Function.

To create a CloudWatch alarm

1. Open the CloudWatch console at https://console.aws.amazon.com/cloudwatch/.

2. Use the region selector to choose the region in which you want to automatically pause email sending.

3. In the navigation pane, choose Alarms.

4. Choose Create Alarm.

5. On the Create Alarm window, under SES Metrics, choose Account Metrics.

6. Under Metric Name, choose one of the following options:

   • Reputation.BounceRate – Choose this metric if you want to pause email sending for your account when the overall hard bounce rate for your account crosses a threshold that you define.

   • Reputation.ComplaintRate – Choose this metric if you want to pause email sending for your account when the overall complaint rate for your account crosses a threshold that you define.

   Choose Next.

7. Complete the following steps:

   • Under Alarm Threshold, for Name, type a name for the alarm.

   • Under Whenever: Reputation.BounceRate or Whenever: Reputation.ComplaintRate, specify the threshold that causes the alarm to trigger.

     Note

     Your account is automatically placed under review if your bounce rate exceeds 5%, or if your complaint rate exceeds 0.1%. When you specify the bounce or complaint rate that causes the CloudWatch alarm to trigger, we recommend that you use values that are below these rates to prevent your account from being placed under review.

   • Under Actions, for Whenever this alarm, choose State is ALARM. For Send notification to, choose the Amazon SNS topic you created in Part 4: Create an Amazon SNS Topic and Subscription.

   Choose Create Alarm.

1. At the command line, type the following command to check the email sending status for your account. Replace region with the name of the Region.

   aws ses get-account-sending-enabled --region region

   If sending is enabled for your account, you see the following output:

   {
       "Enabled": true 
   }

2. At the command line, type the following command to temporarily change the alarm state to ALARM: aws cloudwatch set-alarm-state --alarm-name MyAlarm --state-value ALARM --state-reason "Testing execution of Lambda function" --region region

   Replace MyAlarm in the preceding command with the name of the alarm you created in Part 5: Create a CloudWatch Alarm, and replace region with the Region in which you want to automatically pause email sending.

   Note

   When you execute this command, the status of the alarm switches from OK to ALARM and back to OK within a few seconds. You can view these status changes on the alarm's History tab in the CloudWatch console, or by using the DescribeAlarmHistory operation.

3. At the command line, type the following command to check the email sending status for your account.

   aws ses get-account-sending-enabled --region region

   If the Lambda function executed successfully, you see the following output:

   {
       "Enabled": false
   }

4. Complete the steps in Part 3: Re-Enable Email Sending for Your Account to re-enable email sending for your account.