Creating configuration sets in SES

You can use the SES console, the CreateConfigurationSet action in the Amazon SES API v2, or the aws sesv2 create-configuration-set command in the Amazon SES CLI v2 to create a new configuration set. This section shows how to create configuration sets using the SES console and the Amazon SES CLI v2.

Create a configuration set (console)

To create a configuration set using the SES console, follow these steps:

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

2. In the navigation pane, under Configuration, choose Configuration sets.

3. Choose Create set.

4. Enter the following details in the General details section:

   • Configuration set name – the name for your configuration set. The name can contain up to 64 alphanumeric characters, including letters, numbers, hyphens (-) and underscores (_) only.

   • Sending IP pool – when you send email using this configuration set, messages are sent from the dedicated IP addresses in the assigned pool. Select an IP pool from the list.

     Note

     The default (ses-default-dedicated-pool) contains dedicated IP addresses that haven't been assigned to any other pool. To learn more about managing IP pools, see Assign IP pools.

   • Tracking options – select the Use a custom redirect domain check box to use a custom redirect domain to handle open and click tracking for this configuration set, instead of using one of the SES domains.

     • Custom redirect domain – with a custom redirect domain, you can enter a custom subdomain in the box (optional), or select a verified domain from the list.

     Note

     Custom redirect domains can be specified as follows:

     • Redirect domains must be set up prior to choosing this option. For instructions on selecting a custom domain for handling open and click tracking, see Configuring custom domains to handle open and click tracking.

     • Then, to choose to use a custom redirect domain, you must indicate it while creating your configuration set, or at a later time by editing your tracking options for the configuration set.

   • Advanced delivery options – choose the arrow on the left to expand the advanced delivery options section.

     • Transport Layer Security (TLS) – to require SES to establish a secure connection with the receiving mail server, and send emails using the TLS protocol, select the Required check box.

       Note

       SES supports TLS 1.2 and recommends TLS 1.3. To learn more, see Infrastructure security in SES.

5. Enter the following details in the Reputation options section:

   • Reputation metrics – used to track bounce and complaint metrics in CloudWatch for emails sent using this configuration set. (Additional charges apply, see Price per metric for CloudWatch.)

     • Enabled – select this check box to enable reputation metrics for the configuration set.

6. The Suppression list options section provides a decision set to define customized suppression starting with the option to use this configuration set to override your account-level suppression. The configuration set-level suppression logic map will help you understand the effects of the override combinations. These multitiered selections of overrides can be combined to implement three different levels of suppression:

   1. Use account-level suppression: Do not override your account-level suppression and do not implement any configuration set-level suppression - basically, any email sent using this configuration set will just use your account-level suppression. To do this:

      1. In Suppression list settings, uncheck the Override account level settings box.

   2. Do not use any suppression: Override your account-level suppression without enabling any configuration set-level suppression - this means any email sent using this configuration set will not use any of your account-level suppression; in other words, all suppression is cancelled. To do this:

      1. In Suppression list settings, check the Override account level settings box.

      2. In Suppression list, uncheck the Enabled box.

   3. Use configuration set-level suppression: Override your account-level suppression with custom suppression list settings defined in this configuration set - this means any email sent using this configuration set will only use its own suppression settings and ignore any account-level suppression settings. To do this:

      1. In Suppression list settings, check the Override account level settings box.

      2. In Suppression list, check Enabled.

      3. In Specify the reason(s)..., select one of the suppression reasons for this configuration set to use.

7. The Virtual Deliverability Manager options section provides a way for you to define custom settings for how this configuration set will use engagement tracking and optimized shared delivery by overriding how they’ve been defined in your Virtual Deliverability Manager settings at the account level:

   1. To disable both engagement tracking and optimized shared delivery for this configuration set:

      1. Check the Override account level settings box.

      2. Ensure Enabled is unchecked for both Engagement tracking and Optimized shared delivery, then choose Save changes.

   2. To enable or disable either, or both, engagement tracking and optimized shared delivery for this configuration set:

      1. Check the Override account level settings box.

      2. Check or uncheck Enabled for either or both Engagement tracking and Optimized shared delivery, then choose Save changes.

   3. To revert back to your Virtual Deliverability Manager account level settings for engagement tracking and optimized shared delivery for this configuration set:

      1. Uncheck the Override account level settings box, then choose Save changes.

8. You can optionally add one or more tags in the Tags section. Repeat the following steps for each tag you want to add to your configuration set.

   1. Choose Add new tag.

   2. Enter the tag Key.

   3. Enter the tag Value (optional).

   To remove a tag you've entered, choose Remove for that tag. You can enter a maximum of 50 tags.

9. Choose Create set to create your configuration set.

Now that you’ve created your configuration set, you have the option to define event destinations for your configuration set which enables event publishing that is triggered on the event types you specify for the event destination. A configuration set can have multiple event destinations with multiple event types defined. See Creating Amazon SES event destinations.

Create a configuration set (AWS CLI)

You can create a configuration set using a JSON file as input to the aws sesv2 create-configuration-set command in the AWS CLI.

1. Create a CLI input JSON file

   Use your favorite file editing tool to create a JSON file with the following keys, plus values that are valid for your environment, or use the SES API v2 aws sesv2 create-configuration-set command with the --generate-cli-skeleton option with no value specified to print a sample JSON structure to standard output.

   This example uses a file named create-configuration-set.json:

   {
       "ConfigurationSetName": "sample-configuration-set",
       "TrackingOptions": {
           "CustomRedirectDomain": "some.domain.com"
       },
       "DeliveryOptions": {
           "TlsPolicy": "REQUIRE",
           "SendingPoolName": "sending pool"
       },
       "ReputationOptions": {
           "ReputationMetricsEnabled": true,
           "LastFreshStart": timestamp
       },
       "SendingOptions": {
           "SendingEnabled": true
       },
       "Tags": [
           {
               "Key": "tag key",
               "Value": "tag value"
           }
       ],
       "SuppressionOptions": {
           "SuppressedReasons": ["BOUNCE","COMPLAINT"]
       }
   }

   Note

   • You must include the file:// notation at the beginning of the JSON file path.

   • The path for the JSON file should follow the appropriate convention for the base operating system where you are running the command. For example, Windows uses the backslash (\) to refer to the directory path, and Linux uses the forward slash (/).

2. Run the following command, using the file you created as input.

   aws sesv2 create-configuration-set --cli-input-json file://create-configuration-set.json

Note

To review the AWS CLI reference for this command, see create-configuration-set.