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.
Legitimate B2B outbound on SES in 2026: sandbox exit, SPF/DKIM/DMARC, RFC 8058, Microsoft May 2025 bars, warm-up, and when Pro DIPs beat shared pools — with a first-party compliance checklist.
When to keep Customer.io/Loops vs build journeys with EventBridge + Step Functions + SES — stream isolation, RFC 8058, Pro for DIPs, and a first-party journey architecture checklist.
BIMI on Amazon SES: lab readiness score 38→92 after DMARC quarantine at pct=100, SVG MIME fix, and CloudFront OAC — plus Terraform/CDK and free validators.
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.