Amazon SES

What Amazon SES actually is

Amazon Simple Email Service is AWS's email sending and receiving platform: an API and SMTP interface that applications call to deliver transactional, marketing, and bulk mail. It launched in January 2011 and now carries, in Amazon's own framing, more than a trillion emails a year for customers including Netflix, Duolingo, and Amazon's own retail operation. There is no app to log into, no campaign builder, no contact-list product — SES is plumbing. You bring the content, the list, and the sending strategy; SES brings the IPs, the throughput, and the per-email price that nothing else in the market matches.

That framing matters when comparing SES against tools like Postmark, Mailgun, or SendGrid, which sell a managed sending experience with dashboards, template editors, and support teams who will look at your bounce rates with you. SES sells none of that by default. It sells the pipe. In our view it is the correct choice for a specific profile — engineering teams with volume, who treat email as infrastructure — and the wrong one for anyone who wants a marketing product.

Pricing: what you really pay

The headline rate is the reason SES exists in most stacks: the à la carte plan charges $0.10 per 1,000 outbound emails, with attachment data at $0.12 per gigabyte sent. That rate is not a promotional tier and not a volume commitment; it is the list price for sending without any plan at all, and by our reading of the current pricing page it remains the lowest published per-email rate among established providers.

AWS has recently layered three named plans on top of the à la carte option, priced in volume bands. Essentials runs $0.16 per 1,000 emails up to 10 million per month, $0.14 between 10 and 100 million, and $0.11 above that. Pro adds a base fee (third-party analysis puts it at $105 per account per region per month) at $0.22 / $0.17 / $0.12 per 1,000 across the same bands, and Enterprise starts at $500 per account per region per month at $0.23 / $0.18 / $0.13. Rates apply marginally — each band's rate covers only the emails inside it. The plans buy features (ingress endpoints, tenant management, deliverability tooling) more than they buy a cheaper send rate; at the 0-10M band, à la carte is still cheaper per email than any plan.

The line items that actually move your bill are around the send rate. Dedicated IPs cost $24.95 per month each on the standard tier, or $15 per month per account plus a per-email fee on the managed tier — and at meaningful volume, dedicated IPs are close to mandatory for reputation control. Virtual Deliverability Manager adds $0.07 per 1,000 emails at low volume plus query fees. Incoming mail is charged at $0.09 per 1,000 chunks. None of this is hidden; it is all on one pricing page, which is more transparency than most email providers offer.

The free tier is where we need to correct the internet. The widely repeated claim — 62,000 free emails per month when sending from EC2 — no longer appears on the SES pricing page, and third-party analysis has flagged its removal explicitly. What the product page offers today is up to $200 in AWS Free Tier credits for new customers, with a free plan available for six months after account creation. Budget on that basis, not on the folklore number.

Performance & infrastructure

SES runs in AWS regions, which means the sending infrastructure sits in the same datacenters as the rest of your stack if you are already an AWS customer — same VPC, same IAM, same CloudWatch. That proximity is the performance story: there is no external API hop for an EC2 or Lambda workload, throughput is high by default, and sending scales without you provisioning anything. Global Endpoints, at $0.03 per 1,000 emails on top of the base rate, let a single endpoint configuration fail over across regions — a genuinely useful resilience feature for anyone whose business stops when password-reset emails stop.

Deliverability is the harder half. SES publishes its reputation thresholds as numbers — bounce and complaint rates that will get your account reviewed or restricted — which we consider good practice. Dedicated IPs are available and managed dedicated IPs (where AWS handles warm-up and automatic rotation) exist for a fee. But the sandbox is the defining operational fact of every new account: 200 messages per 24 hours, one message per second, to verified addresses only, with suppression-list APIs disabled until you request production access from AWS Support and pass their review. Public review corpora show that request being refused with some regularity. Plan for days-to-weeks of lead time before SES is a production dependency.

Reliability of the underlying platform is, in our judgment, as good as email infrastructure gets: this is the pipe that carries Amazon's own retail email, including Prime Day. We have not benchmarked SES ourselves — there is no meaningful way to run our standard sysbench/fio/iperf3 suite against an email API — so treat throughput statements as documentation-derived rather than measured.

Where it falls short

The sandbox, first and foremost. Nothing about SES's economics matters if you cannot get production access when you need it, and the approval process is opaque, slow, and demonstrably inconsistent. A launch timeline that depends on SES should treat production access as a risk item with an owner, not an afterthought.

Second, SES is not a product so much as a component. There is no template management with previews, no list hygiene tooling beyond suppression lists and the validation API at $0.01 per validation, no visual campaign builder, and support is standard AWS support unless you pay AWS for more. If your marketing team expects to build newsletters in the tool, SES alone will disappoint them — the common pattern is SES as the send layer behind a tool like Sendy or an in-house dashboard.

Third, cost surprises cluster in the extras. Dedicated IPs, attachment data at $0.12 per GB, VDM per-email fees, and ingress endpoints add up quietly, and the named plans' base fees ($105 and $500 per account per region per month per third-party figures) are real money if you signed up expecting only the per-email rate. Multi-region sending multiplies account-scoped fees.

One comparison we get asked about often: SES versus paying for a mid-tier transactional provider. The per-email gap is real but not the whole calculation. A provider charging several times SES's rate typically includes a sending dashboard, automatic IP warm-up, bounce categorisation you can act on without querying APIs, and a support human who will discuss a sudden complaint-rate spike. Those are products you would otherwise build or buy separately. Our rule of thumb: below roughly a hundred thousand emails a month with no engineer on staff, the SES discount rarely pays for the operational surface you take on; well above it, with engineering already in place, SES is close to unbeatable on cost.

Who should pick this

Our pick for engineering teams already on AWS sending transactional or bulk email at volume who want the lowest defensible per-email cost and can own their deliverability. Password resets, order confirmations, notification digests, product newsletters built in-house — SES does these well and cheaply. It is also the natural choice for cost-sensitive newsletters at scale, provided someone on the team owns IP warm-up and reputation.

Do not pick it if you are non-technical, need production sending within 24 hours of signing up, want an all-in-one marketing suite, or send modest volumes where the engineering time costs more than the per-email savings. At 50,000 emails a month, the à la carte send cost is trivial; the question is whether your team wants to run email infrastructure. If the answer is no, pay a provider that does.

Key takeaways

• Still the cheapest published send rate in the market: $0.10 per 1,000 emails à la carte, attachments $0.12 per GB.
• The famous 62,000-free-emails EC2 tier is gone from the pricing page; today it is up to $200 in Free Tier credits, free plan for six months.
• Every new account starts in a sandbox (200 messages/day, verified recipients) and needs AWS approval to leave — budget lead time.
• Plans (Essentials $0.16/1,000 up; Pro and Enterprise add $105 and $500 monthly bases) buy features, not cheaper sends.
• Infrastructure-grade reliability and AWS integration, but no marketing tooling — SES is a pipe, and the deliverability work is yours.

Sources

• https://aws.amazon.com/ses/pricing/
• https://aws.amazon.com/ses
• https://smtpedia.com/platforms/amazon-ses/review
• https://smtpedia.com/platforms/amazon-ses/pricing