AWS SES: The Cheapest Email That Almost Isn't Worth It

The Weekend I Spent Saving Nine Dollars

It was late 2024. I’d just read, for the hundredth time, that Amazon SES sends email for $0.10 per 1,000. A tenth of a cent per email. My broken-engineer brain lit up like a slot machine. Everyone else was paying $20 a month for Resend, and here was Amazon, quietly offering the same thing for the price of a rounding error. Of course I was going to use it. I’d have been insulted not to.

So I opened the AWS console on a Friday night with a cup of coffee and the confidence of a man who had clearly never opened the AWS console.

By Sunday I had: a verified domain, three DNS records I’d triple-checked, an IAM user with a policy I’d rewritten four times, a support ticket begging Amazon to let me actually send email to strangers, and exactly zero emails delivered to a real human. My “cheapest email in the world” had cost me an entire weekend I’ll never get back.

Here’s the punchline. The volume I was setting all this up for? Maybe 10,000 emails a month. On SES that’s about $1. On ZeptoMail it’s $2.50, and ZeptoMail would’ve taken me fifteen minutes. Over six months, that’s a grand total of about nine dollars saved. I burned a weekend for nine dollars. That, right there, is the entire Broken Engineer disease in one story.

Let me save you the weekend.

---

The Number That Seduces Everyone

I’m not going to pretend the price isn’t real. It is. SES is genuinely, absurdly cheap, and if you’re sending serious volume, nothing on the planet touches it.

I confirmed the current numbers on Amazon’s own pricing page before writing this, because prices drift and I’ve been burned by stale figures before: it’s $0.10 per 1,000 emails, outbound. (Inbound email is priced separately, also at $0.10 per 1,000, but most of us only care about outbound.) There’s no monthly fee, no subscriber count, no plan tier. You send a million emails, you pay a hundred bucks. You send zero, you pay zero.

Compare that to the transactional tools most founders actually use. I broke the full comparison down in the complete SaaS email guide, but the short version:

Sending 100,000 emails/month	What it costs
Resend	~$35/month (Pro tier)
ZeptoMail	~$25 in credits
Amazon SES	~$10

At 100k a month, SES is less than half of ZeptoMail and a fraction of Resend. At a million a month the gap becomes silly — SES stays a flat cheap line while everyone else’s pricing tiers climb. If email is a genuine cost center for your business — you’re sending hundreds of thousands of transactional messages and the bill actually shows up on your P&L — then yes, SES is the answer and I’d stop reading here.

The problem is that almost nobody reading this is at that volume yet. And at low volume, the price advantage is measured in dollars while the setup cost is measured in days.

---

What “Bring Your Own Everything” Actually Means

Here’s the thing nobody tells you when they quote you that $0.10 number. SES isn’t a product the way Resend is a product. Resend hands you a clean dashboard, an API key, and a “you’re done” screen. SES hands you a raw sending endpoint and a shrug.

With Resend or ZeptoMail, you sign up, verify a domain by pasting a few records, grab an API key, and send. Done before your coffee’s cold. With SES, “done” is a much longer list, and you build every item on it:

• IAM. You don’t just get an API key. You create an IAM user or role, write a policy that grants exactly the SES permissions you need (get it wrong and you either can’t send or you’ve handed out god-mode credentials), and generate SMTP credentials separately from your API credentials. This is Amazon’s identity system, and it’s designed for enterprises with a security team, not for you at 1 AM.
• SPF, DKIM, and DMARC. Every good provider makes you set these DNS records, to be fair. But the others hold your hand through it with a checklist and a green tick. SES tells you to figure it out and check back later.
• Bounce and complaint handling. This is the big one. Resend tracks bounces and complaints for you and shows them in a dashboard. On SES, you wire up Amazon SNS (another AWS service) to publish bounce and complaint notifications, then you write the code to consume them, then you actually act on them — because if your bounce or complaint rate creeps too high and you’re not visibly managing it, Amazon puts your sending under review or shuts it off. You are the deliverability team now.
• Everything else. Templates? Basic. Analytics? You pipe events to CloudWatch or build your own. A nice log of what you sent? Build it.

None of this is hard if you already live in AWS. If you don’t, every one of these is a small tutorial, a small gotcha, and a small piece of your weekend.

---

Sandbox Jail

Even after all that, you can’t email anyone yet.

Every new SES account starts in the sandbox. In the sandbox you can send a maximum of 200 emails per 24 hours, at a rate of 1 email per second, and — this is the kicker — only to email addresses you’ve verified in advance. You can email yourself. You can email a test address you own. You cannot email a customer who just signed up, which is the entire reason you wanted email in the first place.

To get out, you file a production-access request. You explain to Amazon how you collect opt-in consent, what kind of mail you send, and how you handle bounces and complaints. As of the last couple of years they also want your SPF, DKIM, and DMARC records already in place before they’ll even consider it. Then you wait — usually 24 to 48 hours, sometimes longer, sometimes they bounce it back asking for more detail and you do the dance again. I’ve seen founders on the AWS forums stuck in a loop, getting rejected, resubmitting, rejected again, with a launch date slipping past them.

When you’re finally approved, you typically start around 50,000 emails a day at 14 per second, which is plenty. But sit with the experience for a second: you signed up for an email service and it wouldn’t let you send email to a customer for two days while a reviewer decided whether you seemed trustworthy. ZeptoMail and Resend had you sending to real inboxes in the time it took SES to load its second onboarding screen.

---

The Free Tier They Quietly Killed

If you read an older tutorial — and a lot of the “just use SES, it’s basically free!” advice online is old — you’ll see a magic number: 62,000 free emails a month. That was real. If your app ran on an EC2 instance, SES used to give you 62,000 outbound emails a month, free, forever. It was genuinely one of the best deals in tech.

It’s gone. Amazon killed that EC2-tied free tier back in August 2023. I mention this because it’s exactly the kind of stale fact that makes a whole blog post look sloppy, and half the internet hasn’t updated.

What exists now is smaller and time-limited: new SES accounts get 3,000 message charges free per month for the first 12 months — and, credit where due, it no longer requires EC2; it works from anywhere. After the first year, or once you cross 3,000, it’s the standard $0.10 per 1,000. And if your AWS account was created after July 15, 2025, you don’t get the SES free tier at all — you get $200 in general AWS credits to spend across services instead.

So the “free” framing is dead. SES is cheap, not free. That’s a different pitch, and it changes the math for a broke founder who was counting on 62,000 free sends.

---

The Hidden Costs Nobody Puts in the Headline

The $0.10 is honest, but it’s the sticker price, not the out-the-door price. A few line items sneak up on you:

• Dedicated IP: if you want a dedicated sending IP (for reputation control at higher volume), that’s $24.95/month for a standard one, or $15/month for a managed one plus per-message usage. That single add-on costs more than a whole year of most people’s actual sending.
• Virtual Deliverability Manager: Amazon’s deliverability dashboard — the kind of thing Postmark just gives you — is an add-on at $0.07 per 1,000 emails, nearly doubling your per-email cost if you turn it on.
• Attachments: you pay $0.12 per GB of attachment data you send.

None of these are outrageous individually. The point is that “SES costs $0.10 per 1,000” is the beginning of the sentence, not the end of it — and the moment you want the conveniences that Resend or Postmark bundle in by default, the gap narrows.

---

So When Is SES Actually Worth It?

I don’t hate SES. I want to be clear about that. It’s a phenomenal piece of infrastructure and it powers a huge chunk of the email on the internet, including some of the very tools I recommend — plenty of “friendly” email SaaS products are just a nice wrapper around SES underneath, and the markup you pay them is the price of not doing what I did that weekend.

Here’s my honest decision tree:

Your situation	Use
Pre-revenue, low volume, want to ship today	Resend free tier, then ZeptoMail
Deliverability is life-or-death (OTPs must land)	Postmark
Already fluent in AWS, IAM doesn’t scare you	Amazon SES
Sending hundreds of thousands / millions a month	Amazon SES, no contest

The pattern: SES wins when you’re either already inside AWS (so the setup cost is near zero for you) or sending enough volume that the price difference is real money. For everyone in between — which is most bootstrapped founders — you’re spending a scarce resource (your time and focus) to save an abundant-enough one (a few dollars a month). That’s a bad trade when you have no users yet and the only thing that matters is shipping.

The same logic is why I tell people to stay away from raw AWS for deployment too. The cloud is unbeatable at scale and brutal before you get there. Email is the exact same story in miniature.

---

The Bottom Line

SES is the cheapest transactional email you can buy, and that number is completely real. But “cheapest” and “best for you right now” are not the same word, and the Broken Engineer in me learned that the expensive way — by spending a weekend, my most finite resource, to shave a dollar off a bill that didn’t exist yet.

If you’re already an AWS shop, or you’re genuinely sending real volume, SES is a gift. Take it. If you’re a solo founder at $0 MRR trying to get your first password-reset email to actually land in an inbox, use ZeptoMail or Resend, ship this afternoon, and come back to SES the day your email bill is big enough to be annoying. It’ll still be $0.10 per 1,000 when you get there.

If email itself still confuses you — transactional versus marketing, why you need two tools, what to actually pay — start with the complete SaaS email guide and the broke solopreneur’s survival guide for the wider stack. And if reading all this made you think “forget the middlemen, I’ll run my own mail server” — I tried that, and here’s why I never do it again.

This is the Broken Engineer Guide. I chase the cheapest number on the page, pay for it with my weekends, and write it all down so you can just ship. Go send an email that lands.