- Click the Enable Message Logs button on the Message Logs page
- Click AWS API button and copy the configuration set name from the code example
- Include the configuration set name in your AWS SES API calls
Example
Emails sent without the configuration set name will not be tracked.
Retrieve Message Events via API
You can programmatically retrieve detailed event history for a specific message using the AWS SESget-message-insights API.
To get the message ID, click the copy button next to the message ID in the
Message Logs table.
Monitor Another Configuration Set
If you want to monitor another configuration set, you should configure your configuration set destination with an SNS topic created by Sendbase. The SNS topic name starts withsendbase-log-<id>.
Tracked Events
| Event Type | Description |
|---|---|
| SEND | Email was successfully sent from SES |
| DELIVERY | Email was successfully delivered to the recipient’s mail server |
| BOUNCE | Email bounced (hard or soft bounce) |
| COMPLAINT | Recipient marked the email as spam |
| REJECT | SES rejected the email (invalid recipient, configuration issues) |
| OPEN | Recipient opened the email |
| CLICK | Recipient clicked a link in the email |
| RENDERING_FAILURE | Email template failed to render |
| DELIVERY_DELAY | Temporary delivery delay occurred |
Data Retention
Email logs are automatically deleted after 7 days to manage storage costs and comply with data retention best practices. An automated cleanup job runs every hour to remove expired logs. If you need longer retention:- Set up your own custom CloudWatch or S3-based logging solution
- Contact support for retention options

