Blog category
Technical guides on Amazon SES configuration, email deliverability, DKIM/DMARC setup, and migrating from SendGrid, Mailgun, or Postmark. Written by engineers who have moved millions of emails per month to AWS SES.
On August 7, 2026 SES added isBotEvent with two values, Likely and Unlikely, on Open and Click notifications. That is 2 of the 10 published event types, and existing configuration-set destinations pick the field up with no new setting.
KumoMTA on AWS production setup: 4 vCPU / 16 GiB baseline per official docs, $200-$610/mo dev footprint, SMTP architecture without ALB, and a 100+ item readiness checklist for self-hosted email infrastructure.
Postal v3 on AWS: 2 vCPU / 4 GiB minimum per official docs, RDS MariaDB production path, $250-$700/mo dev footprint, Docker + Caddy architecture, and 100+ item readiness checklist.
SES tenants (GA Aug 2025) add $0.005/tenant/mo reputation isolation—when ISV platforms need them vs configuration sets alone, with IAM, pricing, and IaC.
SES Global Endpoints (Dec 2024) add $0.03/1k for active-active failover across two regions. MREP decision matrix, replication rules, Tenant Management, and a reproducible readiness benchmark — for architects choosing regional vs multi-region email.
Amazon SES is the most cost-effective email infrastructure for high-volume retail sending — but inbox placement requires dedicated IPs, proper authentication, and automated bounce handling. Here is how to do it right.
Migrating from SendGrid to SES is mostly cheap — until your warm-up plan is wrong and deliverability falls off a cliff. DNS cutover, IP warming, API surface differences, and the deliverability checkpoints that keep email landing in inboxes through the switch.