Monitoring SES events using Amazon EventBridge

Open the Amazon EventBridge console at https://console.aws.amazon.com/events/.

In the navigation pane, choose Developer resources, then select Sandbox, and on the Sandbox page choose the Event pattern tab.

For Event source, choose AWS events or EventBridge partner events.

In the Sample event section, for Sample event type, select AWS events.

For Sample events, scroll down to SES and then select the desired SES event.

EventBridge displays a sample event, along with all of its detail data, for the event type.

You can then use this event to test the event pattern you create in the Event pattern section, or use it as the basis for creating your own sample events for pattern testing covered in the following section.

Open the Amazon EventBridge console at https://console.aws.amazon.com/events/.

In the navigation pane, choose Developer resources, then select Sandbox, and on the Sandbox page choose the Event pattern tab.

For Event source, choose AWS events or EventBridge partner events, and select the sample event you want to test as explained in the previous section.

Scroll down to Creation method, and choose Use pattern form.

In the Event pattern section, for Event source choose AWS services.

Under AWS service, select SES.

For Event type, select the SES event type you want to match.

EventBridge displays the minimum event pattern, comprised of source and detail-type fields, that matches the selected SES event.

In the two examples, the first event pattern matches against all Advisor Recommendation Status Resolved events, and in the second, all Email Bounced events:

{
  "source": ["aws.ses"],
  "detail-type": ["Advisor Recommendation Status Resolved"]
}

{
  "source": ["aws.ses"],
  "detail-type": ["Email Bounced"]
}

To make changes to the event pattern, select Edit pattern and make your changes in the JSON editor.

You can also match on values in one or more detail data fields. This includes specifying multiple possible values for a field value.

In the following example, the detail field was added to the generated minimum event pattern with the data field value specified as DKIM record was not found in order to find all Virtual Deliverability Manager advisor events with the same detail value:

{
  "source": ["aws.ses"],
  "detail-type": ["Advisor Recommendation Status Resolved"],
  "detail": {
    "data": ["DKIM record was not found."]
  }
}

In this example, detail sub-fields were added to report on events generated by all the emails sent from noreply@example.com on 2024-08-05 that bounced. (Prefix matching is being used here as part of Content filtering.):

{
  "source": ["aws.ses"],
  "detail-type": ["Email Bounced"],
  "detail": {
    "mail": {
      "timestamp": [{
        "prefix": "2024-08-05"
      }],
      "source": ["noreply@example.com"]
    }
  }
}

It's important that you read Event patterns in the EventBridge User Guide—it explains that the event pattern value you enter in the JSON editor must be surrounded by square brackets [...] because it's considered an array. This and more information on how to construct advanced event patterns is also provided.

To test if your event pattern matches against the sample event you specified in the Sample event pane above, select Test pattern. If it matches, a green banner at the bottom of the JSON editor will display, "Sample event matched the event pattern".

To troubleshoot errors after selecting Test pattern:

To change the sample values in the Sample event in order to successfully test your Event pattern, in the Sample event pane, select Copy under the JSON editor.

Select the radio button next to Enter my own for Sample event type above the editor.

Paste the sample event into the JSON editor, and for any field you're using in your event pattern, replace that same field's value to match the value you specified in your event pattern.

Scroll back down to the Event pattern pane and select Test pattern again. If all values were entered correctly and match, a green banner at the bottom of the JSON editor will display, "Sample event matched the event pattern".