Emails you when a new bounce / complaint event is triggered in SES. This implements the guidance found in this AWS blog post: https://aws.amazon.com/blogs/messaging-and-targeting/handling-bounces-and-complaints/
Check out this blog post for the details behind why you need to monitor SES bounces / complaints.
To use this workflow, you'll need to first configure a single SNS topic to receive both bounce and complaint notifications from SES. Once created, add that topic as the Bounce Notifications SNS Topic and Complaint Notifications SNS Topic in SES. This single topic will receive both notification types.
Once configured, Fork this workflow to generate an endpoint URL.
Take that endpoint URL and create a new HTTPS subscription on your SNS topic, adding the URL there.
Now, SES will send every bounce or complaint notification to your SNS topic, and SNS will forward those notifications to this Pipedream workflow.
This workflow then forwards that notification to you via email, but you can modify the workflow to handle the notification in any way you'd like (for example, you can send it to Slack or Discord).
In November 2019, SES shipped support for an Account-Level Suppression List. This list helps you stop sending mail to addresses that have previously resulted in a bounce, complaint, or other issue. AWS notes:
If you attempt to send a message to an address on the account-level suppression list, Amazon SES accepts the message, but doesn't send it.
If you've added an address to this list, SES will still send a bounce notification of bounce sub-type OnAccountSuppressionList to your SNS topic, which gets forwarded to this workflow. This workflow ignores messages with this bounce sub-type.
See these instructions from AWS for how to enable the account-level suppression list and add new addresses to it.