If you've priced out email marketing platforms lately, you've probably had the same realization every founder and growth engineer eventually does.
Amazon SES sends email for about ten cents per thousand. Mailchimp, SendGrid, and the rest charge multiples of that for what is, underneath, the same sending. So the obvious question becomes: why not run your marketing and bulk email through AWS SES directly?
The answer is yes, you absolutely can, and it's exactly what SES was built for. But the setup has a few steps people miss, and the deliverability side is where most first-timers quietly fail. Here's the full picture.
What AWS SES is actually built for
Amazon SES is a cloud email delivery service designed for transactional and permission-based marketing email. Order confirmations, password resets, newsletters, product updates, re-engagement campaigns, and any email going to a list of people who opted in to hear from you.
The key word is permission. SES expects you to send to recipients who signed up, and it expects you to keep bounce and complaint rates low. Stay inside those lines and SES is one of the most cost-effective, high-deliverability sending backbones available. It's the same infrastructure a huge number of SaaS products already use behind the scenes.
Where SES differs from a tool like Mailchimp is that it gives you the sending engine and leaves the campaign layer to you. No drag-and-drop builder, no built-in list management UI, no dashboard full of open-rate charts out of the box. That's the tradeoff for the price.
The AWS SES setup for marketing email, step by step
Here's what getting SES ready for marketing campaigns actually involves.
Verify your sending domain. Add your domain in the SES console and publish the DNS records it provides. This proves you own the domain you're sending from and is the foundation everything else builds on.
Set up DKIM. SES generates three CNAME records through Easy DKIM. All three go into your DNS. DKIM cryptographically signs your outgoing mail so receiving servers can confirm it wasn't altered in transit. This is one of the single biggest factors in whether you land in the inbox rather than the promotions tab or spam.
Configure a custom MAIL FROM domain. By default SES sends with a bounce address on amazonses.com, which fails DMARC alignment for your own domain. Setting a custom MAIL FROM subdomain like mail.yourdomain.com fixes this and looks more professional. Most people skip this and then wonder why their DMARC never fully passes.
Publish SPF and DMARC. SPF authorizes SES to send on your behalf. DMARC ties SPF and DKIM together and tells receiving servers what to do when authentication fails. Start DMARC in monitoring mode, confirm your legitimate mail is passing, then move it to enforcement. This matters more than ever now that Gmail and Yahoo require it from bulk senders.
Request production access. New SES accounts start in a sandbox that only sends to verified addresses, capped around 200 emails a day. To send to your real subscriber list you file a production access request describing your use case and list source. Approval usually takes 24 to 48 hours.
Set up bounce and complaint handling. This is the step people skip and regret. SES pushes bounce and complaint events through SNS. If you aren't capturing those events and automatically suppressing bad addresses, your numbers climb until AWS steps in. Automatic suppression is not optional for serious sending.
None of this is beyond a technical person. But notice how much of it has nothing to do with writing a good campaign. It's infrastructure.
Why marketing senders still land in spam on SES
Here's what catches people off guard. SES having great deliverability infrastructure does not guarantee your emails reach the inbox. That part is on you, and it comes down to a handful of fundamentals.
Warm up your sending. Going from zero to fifty thousand emails overnight looks like spam infrastructure to every mailbox provider. Start with your most engaged subscribers and ramp volume gradually over days or weeks.
Keep your list clean. Remove hard bounces and complaints immediately. Prune subscribers who haven't opened anything in six months. Every bounce and complaint chips away at your sender reputation, and on SES a rising complaint rate is the number that gets your account reviewed.
Authenticate and keep it authenticated. SPF, DKIM, and DMARC aren't set-and-forget. DNS records change and break silently. A DKIM selector that passed three months ago can fail today without any error you'd notice until deliverability drops.
Watch your content. Spam trigger words, a bad text-to-image ratio, and too many links all get scored by filters before a human opens the email. Modern filters at Gmail and Outlook are aggressive, and a single bad template can tank an otherwise clean campaign.
Check blacklist status regularly. A clean domain can land on Spamhaus or Barracuda overnight. Checking once at setup and never again is how senders get blindsided mid-campaign.
Include a working one-click unsubscribe. Gmail and Yahoo now require it for bulk senders. Beyond compliance, an easy unsubscribe is better for your reputation than forcing frustrated recipients to hit the spam button instead.
The setup most teams actually land on
After wiring up SNS pipelines and hand-rolling warmup logic once, most founders and marketing teams arrive at the same conclusion. They want the SES sending rate, but not the job of being their own deliverability engineer.
The pattern that solves this is connecting your own SES account to a layer that handles the parts SES leaves to you: the DKIM and MAIL FROM setup, automatic warmup, bounce and complaint processing, and a pre-send check on every campaign. You still pay AWS directly for sending at ten cents per thousand, and a flat rate for the software that keeps you out of trouble and gives you the campaign tools SES doesn't include.
A handful of tools do this now. EmailQo is one built specifically around connecting your own AWS SES account, if you want SES economics without building the deliverability plumbing yourself. And if you're still weighing SES against sending through a Gmail or Outlook account to start, this AWS SES vs Gmail comparison lays out when each one makes sense.
The reason this shape wins comes down to who's reading. A founder gets SES pricing without needing to be an infrastructure engineer. An agency runs each client on isolated, owned infrastructure instead of a shared pool where one bad client sinks everyone's deliverability. A marketing team sends at volume with the campaign tools they actually need on top.
The bottom line
AWS SES being cheap was never the hard part. Ten cents per thousand emails is real, and for founders, agencies, and marketing teams it's a genuinely good deal.
The hard part is everything around the sending. The setup that has nothing to do with your actual campaign. The reputation you have to build first and then protect. The authentication that breaks quietly while your dashboard still looks green.
Sort that out, and the cheap sending rate finally starts to mean something. Skip it, and you'll be back to an expensive platform within a month, wondering where your open rates went.