What it does
Every email the product sends goes through one outbound path with one suppression list and one audit log. Amazon SES can be the service that path delivers through, using your own AWS account — so sending happens in the SES region you choose, under your AWS agreement. Bounce and complaint notifications come back through Amazon SNS and update your suppression list and email dashboard.
Setup steps
1. In AWS, verify your sending domain in SES (DKIM and SPF), request production access to leave the SES sandbox, and create an IAM user allowed to send through SES.
2. In your email settings, add a sender, choose Amazon SES, and enter the access key ID, the secret access key, the SES region, and optionally a configuration set. A workspace admin can do this; it does not need us.
3. Open "Test webhook" on that sender. It shows the bounce and engagement addresses for it — subscribe them to your SES notifications through SNS.
4. Send a test email from the same screen and check it arrives.
What you get
- Your region, your account. Sending runs in the SES region you enter, from your AWS account.
- Bounces and complaints handled. They add the address to your suppression list, so no module emails it again.
- Delivery you can see. The email dashboard shows deliveries, bounces and complaints across every module.
- No double sends. Every send carries an idempotency key; a repeat within 24 hours returns the first send instead of sending again.
Verified notifications
Every SNS notification is checked against Amazon's signature before anything is recorded, and one that fails is rejected. Subscription confirmations are handled automatically.
Related
See the Email module for the outbound path this plugs into. Other senders: Postmark, Resend, Mailgun.