Amazon SES’s send API confirms exactly one thing: that SES accepted your message and will attempt delivery. It says nothing about whether the message arrived, bounced, got marked as spam, or was ever opened. A configuration set is what closes that gap. Attach one to a send, and SES reports on what happened to it as a stream of events. Skip it, and the API’s initial success is the last thing you hear.
Key Takeaways
- A configuration set is a named set of rules you attach to a send. On its own it does nothing; it needs one or more event destinations added to it.
- SES can publish ten event types: Send, Delivery, Bounce, Complaint, Reject, DeliveryDelay, RenderingFailure, Subscription, Open and Click.
- Open and Click are two separate check boxes on the event destination itself, under “Open and click tracking.” Leave them unchecked and those two events never fire.
- Four destinations are worth using: CloudWatch for running totals, SNS for real-time notifications, Amazon Data Firehose for the raw event stream, and EventBridge for routing one event to several places at once.
- Without a configuration set on a send, the event stream never reaches you. You get a message ID in the API response, plus plain-text bounce and complaint emails from SES.
What a configuration set is
A configuration set is a named set of rules you attach to a send, either by naming it on the send call or by making it the default configuration set for a verified identity. On its own, a configuration set does nothing. It needs one or more event destinations added to it, and each destination names which event types to publish and which AWS service to publish them to. Creating the set and adding a destination to it are two separate steps in the SES console, and one configuration set can carry more than one destination if you want the same events routed to more than one place.
Naming the configuration set is one line in the send call:
{
"FromEmailAddress": "hello@example.com",
"Destination": { "ToAddresses": ["subscriber@example.com"] },
"ConfigurationSetName": "marketing-example",
"Content": {
"Simple": {
"Subject": { "Data": "Your November update" },
"Body": { "Text": { "Data": "..." } }
}
}
}
Nothing forces one configuration set for a whole account. A common split pairs one configuration set, and one dedicated IP pool, with marketing sends, and another with transactional sends, so a campaign’s bounce volume never gets folded into the same reputation numbers as a password reset. Dedicated IPs: who needs one covers when that separation is worth the extra infrastructure.
SES also lets you attach message tags, name and value pairs, to a send, and adds a handful of its own auto-tags: which configuration set handled the send, the domain in the “From” address, the IP SES sent from. A CloudWatch destination can turn any of those tags into a dimension, which is how one configuration set ends up reporting separately by campaign, or by client, without a code change beyond adding the tag.
The ten events a configuration set can publish
SES defines ten email sending event types:
| Event | What it means |
|---|---|
| Send | SES accepted the message and will attempt delivery. |
| Delivery | SES successfully delivered the message to the recipient’s mail server. |
| Bounce | A hard bounce: the recipient’s mail server permanently rejected the message. A soft bounce only reports once SES stops retrying, not on the first attempt. |
| Complaint | The message was delivered, and the recipient marked it as spam. |
| Reject | SES accepted the message, found a virus in it, and never attempted delivery. |
| DeliveryDelay | A temporary problem, a full inbox or a transient server issue, is holding up delivery. |
| RenderingFailure | A templated send failed because the template data didn’t match its parameters. Only occurs on SendTemplatedEmail or SendBulkTemplatedEmail. |
| Subscription | The recipient used the List-Unsubscribe header or an unsubscribe link to update their preferences. |
| Open | The recipient opened the message. |
| Click | The recipient clicked a link in the message. |
A Bounce event’s timing is worth knowing before you build anything on top of it: see reading a bounce for why a soft bounce doesn’t show up the moment it happens.
Open and Click sit apart from the rest. On the event destination’s select event types step they are two check boxes under “Open and click tracking,” not part of the sending and delivery list above them. Leave them unchecked and SES never generates those two events, whatever destination you’ve wired up. Virtual Deliverability Manager has a setting also called engagement tracking, and it is a different thing: AWS states that disabling it “will not disable the open and click event publishing you have set up here in SES event destinations.”
Where an event can go
Each event destination points at one AWS service. SES’s console also still lists Amazon Pinpoint, but Pinpoint ends support on October 30, 2026, so that leaves four:
| Destination | What it’s for | What you get |
|---|---|---|
| Amazon SNS | Real-time notifications | One message per event, published to a topic the moment it happens |
| Amazon CloudWatch | Running totals and dashboards | Aggregated metrics by event type and the dimensions you choose, not individual records; incurs CloudWatch detailed-monitoring charges |
| Amazon Data Firehose | Bulk analysis downstream | The full stream of raw event records, batched and delivered to wherever the Firehose delivery stream points, such as a data lake or a warehouse |
| Amazon EventBridge | Routing to multiple targets | Events land on an EventBridge event bus, which can fan them out to several targets at once |
Which destination fits which job
Pick by what you’ll do with the event, not by which destination sounds most capable. Wanting a number that goes up or down, sends today against yesterday, points at CloudWatch. Wanting to react to a single event as it happens points at SNS, which is also the destination the SES console itself recommends when you want a notification rather than a metric. Wanting the raw event history in a data lake or a warehouse for later analysis points at Firehose. Wanting one event routed to several systems at once, rather than building that fan-out yourself, points at EventBridge, the only one of the four built for it.
Nothing stops you running more than one destination on the same configuration set. A common pairing is CloudWatch for the dashboard and SNS for the notification, both fed from the same events, since a destination only decides where an event goes, not which events exist.
Setup cost varies too. EventBridge needs nothing at the destination end: it always publishes to your account’s default event bus, no bus to create. SNS lets you create a new topic inline during the same setup flow instead of requiring an existing one. Firehose asks for more, an existing delivery stream and an IAM role SES can assume to write to it. CloudWatch events are billed as detailed monitoring, so each unique combination of event type and dimension becomes its own metered metric, not a free one.
What happens without a configuration set
No configuration set on a send means no event destination reads that send, whatever destinations exist on other configuration sets in your account. The API response is the main signal you get back: a message ID confirming SES accepted the request. Deliveries, opens and clicks reach you only if a configuration set on that specific send says where to publish them. Bounces and complaints can also arrive as plain emails to the address on the identity, but that is not something you can build on. Bounces, complaints and suppression in SES covers the account-level suppression list, which keeps working with or without a configuration set and stops SES from re-delivering to a bad address. It’s not the same as knowing what happened to a specific message, which is what event publishing is for.
Why to set it up before the first send
Setting up a configuration set and an event destination costs a few minutes in the console, once, before the first send. Skipping it costs nothing until the first bounce spike or complaint problem, and by then there’s no event history to look back on: events that were never published can’t be retrieved later, whatever destination you add. Getting out of the SES sandbox already asks for this in practice. AWS’s own production access review wants to know what happens to a bounce or a complaint, and “an SNS notification into an automated suppression step” is the kind of answer it’s looking for. You can only give that answer if the configuration set already exists.
The permissions a connected AWS account grants for this, and what they’re scoped to, are covered in connecting an AWS account safely.
Frequently asked questions
What is an Amazon SES configuration set?
A configuration set is a named set of rules you attach to a send, either by naming it on the API call or by making it the default for a verified identity. On its own it does nothing: you have to add one or more event destinations to it before Amazon SES reports anything back about what happened to your message.
How many event types can Amazon SES publish?
Amazon SES defines ten email sending event types: Send, Delivery, Bounce, Complaint, Reject, DeliveryDelay, RenderingFailure, Subscription, Open and Click (AWS’s event publishing documentation). Which of them you actually receive depends on which events you’ve told your event destination to publish.
Do I need to turn on anything extra to get Open and Click events from Amazon SES?
Yes. On the event destination, Opens and Clicks are two check boxes under “Open and click tracking,” separate from the sending and delivery event types. Leave them unchecked and Amazon SES never generates those two events, no matter which destination you’ve wired up. The engagement tracking setting in Virtual Deliverability Manager is unrelated and does not switch event publishing on or off.
What’s the difference between Amazon SNS and Amazon EventBridge as SES event destinations?
Amazon SNS publishes one message per event to a topic the moment it happens, which is what you want for a real-time notification. Amazon EventBridge routes events onto an event bus that can fan them out to several targets at once, which is what you want when more than one system needs to react to the same event.
Does Amazon CloudWatch cost extra for SES event monitoring?
Yes. CloudWatch events from Amazon SES are billed as detailed monitoring, so each unique combination of event type and dimension becomes its own metered metric rather than a free one. The other three destinations, SNS, Firehose and EventBridge, don’t carry that same per-metric charge.
What EmailFig sets up for you
Connect your own AWS account, and EmailFig creates a configuration set and an SNS event destination for your sending domain before your first campaign goes out. Connect your own Amazon SES account has the exact permissions involved. The practical result is that delivery, bounce, complaint and engagement data start flowing from your first send, not from whichever send happens after you notice something’s missing.