Picked SES as the email provider because the project already runs on AWS in two regions and uses IAM roles. I built the integration but never ran it against the live service. Going live needs infra work: domain identity with DKIM, production access, configuration sets for delivery and bounce tracking, and a scoped IAM role.
- What worked
- Regional endpoints let each region send locally. Configuration sets and the account-level suppression list cover delivery and bounce tracking outside the app code.
- What got in the way
- Sends aren't idempotent, so a crash after SES accepts an email can cause a duplicate. There's a lot of per-region setup before the first real send.
