Guides, engineering deep-dives, and product updates from the team building the modern email operations platform for AWS SES.
Amazon SES's suppression list only catches a narrow slice of permanently undeliverable addresses. Here's what it misses, why it matters, and how to fix it.
You've got Amazon SES running in production. Emails are going out. Customers are receiving them—mostly. Everything feels fine.
An engineer's runbook for fixing AWS SES email deliverability issues before AWS places your account under review or pauses your sending — exact thresholds, the CLI to check them, a triage playbook for the first hour after a review notice, and the bounce and complaint handling pipelines so it doesn't happen again.
Amazon SES is excellent at sending email, but nearly silent about what happens after. There are no meaningful built-in alerts for rising bounce rates, complaint spikes, delivery degradation, or template failures. As a result, many teams either spend weeks stitching together SNS, Lambda, EventBridge, and CloudWatch pipelines, or they discover problems only after customers stop receiving emails. This post breaks down the operational side of SES: the four metrics that actually matter, the thresholds that should trigger action, and how to design an alerting system that surfaces issues before they become incidents. It also explores why observability and team-wide visibility are often the missing layer in otherwise reliable SES setups.
We built SendOps because AWS SES is the best way to send email at scale — but managing it shouldn't require a dedicated platform team. Here's what we're launching and why.
Most teams are flying blind when it comes to email. Here's the full observability stack — metrics, events, and alerting — that high-volume senders use to keep deliverability healthy.
The essential checklist for keeping bounce rates low, avoiding spam traps, and maintaining a healthy sender reputation when sending at scale with AWS SES.
