Amazon SES in short
Amazon SES is the cheapest way to send email at scale — $0.10 per 1,000 outbound — and the most DIY: it is a set of AWS console switches, not a product surface. The free tier meters "message charges" for the first 12 months and then rolls into pay-as-you-go on its own; mailbox-simulator test sends are billed like production mail; and opening a technical support case requires a $29/mo AWS Support plan, below which it is forum answers. AWS publishes an entire billing page called "Understanding unexpected charges" — which tells you the culture.
Verdict: Unbeatable per-email price, most expensive per hour of attention. You're buying raw send rate and taking on deliverability, monitoring and billing guardrails yourself — and the surprise-bill stories on r/aws are a platform feature, not an anomaly.
Frequently asked questions
Why did my SES bill spike while I thought I was on the free tier?
The free tier meters "message charges" for 12 months and then converts to pay-as-you-go automatically. AWS's own billing docs carry an "Understanding unexpected charges" page, and r/aws threads on surprise bills end with the same advice: open a billing case and ask nicely.
Is SES cheaper than a developer email API?
Per email, almost always. Per hour of engineering time, rarely: deliverability tooling, suppression and monitoring are yours to build, and support starts at $29/mo.
Does SES receive email?
Yes — inbound is billed per message received. But parsing, storage and routing happen through S3 and Lambda: it's assembly work, not a shared inbox.
Do test sends cost money?
Yes. "We do charge you for each message you send to the mailbox simulator, just as if they were messages you sent to actual customers."
When is SES the right call?
High volume, low ceremony: you already have the AWS account, you'll set billing alarms, and you'd rather pay $0.10 per thousand than a monthly plan.