Amazon SES email marketing means using Amazon Simple Email Service as the delivery engine for newsletters, promotions and automated journeys, while a separate tool handles your lists, campaigns and unsubscribes. AWS explicitly supports marketing email on SES, delivery costs a fraction of contact-based platforms, and you take on more responsibility for setup and list hygiene. This guide covers what SES does and does not do, what you need to start, three ways to build your stack, real monthly costs at 10,000, 50,000 and 100,000 contacts, and the cases where SES is the wrong choice.

Key takeaways

  • SES is a sending service, not a marketing app: it delivers mail and reports bounces and complaints. You still need software for lists, campaign building, segments and reporting.
  • Marketing email is allowed: the production access form has a "Marketing" mail type, but the AWS Acceptable Use Policy bans unsolicited mass email, so opt-in lists only.
  • Delivery is cheap: as of November 2026, new accounts start on the Essentials plan at $0.16 per 1,000 emails, and you can switch to à la carte at $0.10 per 1,000. A 50,000-contact list mailed weekly costs about $20 to $32 a month to deliver.
  • You own deliverability: AWS places accounts under review at a 5% bounce rate or a 0.1% complaint rate. Bounce and complaint processing is your job (or your tool's).
  • Not for everyone: tiny lists, purchased lists and teams with nobody to touch DNS are better served by an all-in-one platform.

What Amazon SES is (and what it is not)

Amazon SES is infrastructure. You hand it a message through the SES API or SMTP, it signs the message with DKIM, delivers it from AWS sending IPs, and reports what happened: delivered, bounced, complained, opened or clicked if you enable tracking. It is the same category of product as SendGrid's or Mailgun's sending APIs, not the same category as Mailchimp.

SES does have a few list features that surprise people. The SES API v2 offers a contact list with up to 20 topics, a hosted unsubscribe page, and automatic List-Unsubscribe headers when you send with ListManagementOptions. But the SES list management documentation also says only one contact list is allowed per AWS account, and every operation is an API call. There is no campaign editor, scheduler or segment builder in the console.

JobDoes SES do it?Who usually does it
Deliver email over API or SMTPYesSES
DKIM signing (Easy DKIM)YesSES, after you publish 3 CNAME records
Bounce and complaint notificationsYes, via SNS, EventBridge or emailSES sends them; your tool must act on them
Suppress hard bounces and complaintsYes, account-level suppression listSES plus your own list
Open and click trackingYes, through configuration setsSES or your marketing tool
Store contacts with custom fields and tagsBasic (one contact list, API only)Marketing tool
Signup forms and double opt-inNoMarketing tool or your website
Drag-and-drop editor, templates galleryNo (API templates only)Marketing tool
Segments, scheduling, A/B testsNoMarketing tool
Automation journeys (welcome, re-engagement)NoMarketing tool or your code
Campaign reports per sendRaw events onlyMarketing tool

That split is the whole idea behind bring-your-own sending: you rent delivery from AWS and pair it with software for everything above it. Our explainer on what BYO email is covers the model in more depth.

Does AWS allow Amazon SES email marketing?

Yes. When you request production access, the SES console asks you to choose between Marketing and Transactional as the type that best describes most of your mail. AWS defines marketing email as mail "sent on a one-to-many basis to a targeted list of prospects or customers" with promotional content, so newsletters and promotions are an expected use.

The limit is consent. The AWS Acceptable Use Policy prohibits using AWS "to distribute, publish, send, or facilitate the sending of unsolicited mass email." The SES sending review FAQ defines unsolicited email as mail the recipient did not explicitly ask for, including sending advertisements to people who only signed up for notifications. In the production access form you must tick an acknowledgement that you only send to people who explicitly requested your email and that you have a process for bounce and complaint notifications.

In practice: opt-in newsletters, customer promotions, product updates and lifecycle emails are fine. Purchased lists, scraped lists, "cold outreach at scale" and old lists you have not mailed in years are exactly what gets SES accounts paused.

What you need before your first campaign

Here is the minimum stack. Each item links to a step-by-step guide.

  1. An AWS account and one SES region. Sandbox status, quotas, identities and even your pricing plan are set per region, so pick one (usually the region closest to your audience or your other AWS resources) and stay there.
  2. A verified sending domain. Create a domain identity and publish the three Easy DKIM CNAME records. Walkthrough: how to verify a domain in Amazon SES.
  3. SPF alignment and DMARC. Optional in SES itself, effectively required by Gmail and Yahoo for bulk senders. See the SPF, DKIM and DMARC setup guide.
  4. Production access. New accounts start in the sandbox: verified recipients only, 200 messages per 24 hours and 1 message per second. Details and the approval tips that matter are in our Amazon SES sandbox guide.
  5. Enough quota for your list. After approval, AWS sets your daily quota and send rate based on your use case. If your biggest send is larger than your 24-hour quota, request an increase first. See Amazon SES sending limits.
  6. Credentials for your tool. Either IAM access keys for the API or SMTP credentials generated in the console. Hostnames and ports: Amazon SES SMTP settings.
  7. Bounce and complaint handling. A configuration set or identity notifications publishing to SNS, plus something that removes those addresses from your list. Setup: Amazon SES bounce and complaint handling.
  8. A tool for lists, campaigns and unsubscribes. This is the architecture decision covered next.

Three ways to run Amazon SES email marketing

Every SES marketing setup is one of three shapes. The right one depends on who maintains it, not on which is cheapest on paper.

1. Code it yourself

Your application stores subscribers, renders templates and calls SendEmail or SendBulkEmail. You subscribe an SNS topic to bounce and complaint events and write the handler that flags those contacts. This is common for SaaS products that already have a user database and only need product newsletters.

The hidden work is everything a marketer will ask for later: a preview, a test send, a segment by plan type, a resend to non-openers, a report the CEO can read. Each one is a feature you build and maintain. Budget for the developer time, which almost always exceeds the SES bill.

2. Self-hosted app on your own server

Apps like Sendy and listmonk give you a web interface on top of SES. As of November 2026, Sendy lists a one-time license of $69 and runs on PHP and MySQL hosting; listmonk is free, open source and runs as a single binary with PostgreSQL. You pay for the server, and you own updates, backups, security patches and the cron jobs that process bounces.

This route suits developers who enjoy running servers. Read our Sendy review and the broader guide to self-hosted email marketing before committing, because the trade-offs show up months later, usually during an upgrade or a server migration.

3. Managed BYO platform

A hosted platform connects to your SES account with credentials you provide. You get the editor, segments, automation and reporting without running a server, and you keep paying AWS directly for delivery. eMailBase works this way: you add SES (and optionally SendGrid, Mailgun or any SMTP server) as sending servers, then run campaigns and automation workflows in the browser. Plans have contact limits, starting at $4.99 a month for 5,000 contacts.

ScenarioCode it yourselfSelf-hosted appManaged BYO platform
Time to first campaignWeeksHours to a dayUnder an hour after SES is ready
Software costDeveloper timeLicense (or free) plus hostingMonthly subscription
Who patches and backs upYouYouThe vendor
Bounce processingYou write itBuilt in, you keep it runningCheck how the vendor handles it
Marketer can work aloneNoMostlyYes
Best forSaaS with in-house engineersTechnical solo founders, agencies with ops skillsMarketing teams, agencies, nonprofits

Whichever route you choose, confirm three things: how unsubscribes are recorded, how SES bounce and complaint events reach the tool, and whether you can export your contacts at any time.

Amazon SES email marketing costs at 10k, 50k and 100k contacts

SES bills per recipient, not per contact stored. The Amazon SES pricing page lists these rates as of November 2026:

  • Essentials plan (default for new accounts since July 21, 2026): $0.16 per 1,000 emails for the first 10 million each month.
  • À la carte (switch any time): $0.10 per 1,000 emails.
  • Data: $0.12 per GB. AWS labels it attachment data, but its own worked examples apply it to the full message size, so we include it.
  • Pro ($0.22 per 1,000 plus $105 a month) and Enterprise ($0.23 per 1,000 plus $500 a month) add managed dedicated IPs, email validation and other features most newsletter senders do not need at these volumes.

Assumptions for the table: four campaigns a month to the whole list, an average message of 50 KB (0.00005 GB), shared IPs, and eMailBase as the software on monthly billing.

Line item10,000 contacts50,000 contacts100,000 contacts
Emails per month (contacts × 4)40,000200,000400,000
SES à la carte ($0.10 per 1,000)$4.00$20.00$40.00
SES Essentials ($0.16 per 1,000)$6.40$32.00$64.00
Data (GB × $0.12)2 GB = $0.2410 GB = $1.2020 GB = $2.40
eMailBase planGrowth $9.99 (20k)Pro $19.99 (50k)Business $34.99 (200k)
Total, à la carte$14.23$41.19$77.39
Total, Essentials$16.63$53.19$101.39

The arithmetic for the middle column: 200,000 ÷ 1,000 × $0.10 = $20.00; 200,000 × 0.00005 GB = 10 GB, × $0.12 = $1.20; plus $19.99 for the software, giving $41.19. On Essentials, the delivery line becomes 200 × $0.16 = $32.00, for $53.19 in total. eMailBase plans cost 20% less billed every six months and 35% less billed annually.

Two things move these numbers more than anything else: send frequency (doubling to eight sends a month doubles the SES line, not the software line) and whether your list sits near a plan's contact limit. For the full price breakdown, including when Essentials is actually cheaper than à la carte, see Amazon SES pricing explained. To compare against contact-based platforms, read why Mailchimp gets expensive and our email marketing cost guide. If price is the only criterion, the cheapest way to send bulk email compares every route.

New AWS account?

As of November 2026, AWS says new customers receive up to $200 in Free Tier credits usable on eligible services including SES, with a free plan available for 6 months after account creation. Credits must be used within 12 months.

The deliverability responsibilities you take on

On an all-in-one platform, the vendor quietly blocks bad imports and processes bounces for you. On SES, AWS watches the outcome and you manage the inputs. These are the five areas you own.

1. Authentication

Easy DKIM covers DKIM. For SPF to align with your From domain (which DMARC alignment through SPF requires), set up a custom MAIL FROM subdomain such as bounce.example.com. Then publish a DMARC record. Google's email sender guidelines require SPF, DKIM and DMARC for anyone sending more than 5,000 messages a day to Gmail accounts.

2. Bounces and complaints

The SES sending review FAQ publishes the thresholds:

MetricAWS recommendsAccount placed under reviewSending may be paused
Bounce rate (hard bounces only)Below 2%5% or higher10% or higher
Complaint rateBelow 0.1%0.1% or higher0.5% or higher

Rates are calculated over a "representative volume" rather than a fixed date range, so you cannot recompute them exactly from your own stats. Watch the Reputation metrics page in the SES console and set CloudWatch alarms well below the review lines. Our bounce and complaint handling guide includes the SNS setup.

3. Suppression

Accounts created after November 25, 2019 use the account-level suppression list for bounces and complaints by default. It is a safety net, not list hygiene: SES still counts messages to suppressed addresses toward your daily quota. Remove those contacts from your marketing list too.

Blind spot: AWS states that Gmail does not provide complaint data to SES. A Gmail user clicking "Spam" will not appear in your SES complaint rate or suppression list. Monitor Gmail separately with Google Postmaster Tools, and keep Google's spam-rate limit of 0.30% (target below 0.10%) in mind.

4. Unsubscribes

Every marketing email needs a visible unsubscribe link, and Gmail requires one-click unsubscribe for bulk marketing mail. If you use SES subscription management, SES adds the headers for you; otherwise your tool must. Confirm which one is doing it before your first campaign. Our bulk sender requirements guide lists what each mailbox provider checks.

5. IPs, warm-up and tracking

New accounts send from shared AWS IPs, which is the right choice for most marketers. AWS's own guidance is that dedicated IPs suit large, regular, predictable volume. If you are considering one, read Amazon SES dedicated IP first. Whatever the IP, ramp volume gradually on a new domain using the IP and domain warmup guide. Open and click tracking works through configuration sets, with caveats explained in Amazon SES open and click tracking.

If mail still lands in spam after all of this, work through why emails go to spam before changing providers.

A 30-day Amazon SES email marketing setup roadmap

This is the order that avoids rework. Most of the calendar time is DNS propagation and AWS review, not hands-on work.

Days 1 to 2: account, region and domain

  1. Create or choose the AWS account and enable MFA on the root user. Create an IAM user or role for SES only.
  2. In the SES console, pick your region. Under Configuration > Identities, choose Create identity > Domain.
  3. Publish the DKIM, MAIL FROM and DMARC records. They look like this (replace the tokens and region with the values the console shows):
; Easy DKIM (3 records) tok1._domainkey.example.com CNAME tok1.dkim.amazonses.com tok2._domainkey.example.com CNAME tok2.dkim.amazonses.com tok3._domainkey.example.com CNAME tok3.dkim.amazonses.com ; Custom MAIL FROM subdomain bounce.example.com MX 10 feedback-smtp.us-east-1.amazonses.com bounce.example.com TXT "v=spf1 include:amazonses.com ~all" ; DMARC (start in monitoring mode) _dmarc.example.com TXT "v=DMARC1; p=none; rua=mailto:dmarc@example.com"

AWS notes that the MAIL FROM subdomain must have exactly one MX record, and detection can take up to 72 hours.

Days 2 to 6: production access

  1. Once the domain shows Verified, go to Account dashboard > View Get set up page > Request production access.
  2. Choose Marketing, give your website URL, and describe how people opt in, how they unsubscribe, and how you process bounces. Be concrete: "Visitors subscribe through a double opt-in form on example.com/newsletter."
  3. AWS says the initial response comes within 96 hours. If they ask questions, answer the specific question; vague replies slow approval.

Days 3 to 7: connect your tool and wire up events

  1. Create a configuration set, add an event destination for bounces and complaints (SNS), and enable open and click tracking if you want it.
  2. Generate SMTP credentials or API keys and connect your marketing tool.
  3. Send test messages to the SES mailbox simulator (for example bounce@simulator.amazonses.com) and confirm the bounce lands on the right contact in your tool.

Days 7 to 10: prepare the list

  1. Import only contacts who opted in. Drop role addresses you never collected through a form and anything that has not engaged in a long time.
  2. Build an "engaged" segment (opened or clicked recently, or joined recently). Our list building and segmentation guide shows how.
  3. Run a spam-score check on your first template, and read the AI copywriting and spam score guide if your copy is promotional.

Days 10 to 30: warm up and scale

  1. Send to your most engaged contacts first, then increase volume every few days while bounce and complaint rates stay low.
  2. Check Reputation metrics after every send. If bounce rate climbs past 2%, stop and clean the segment before continuing.
  3. Once the full list is mailed cleanly, set DMARC to p=quarantine after reviewing your reports.
  4. Optional: add a second provider for failover, as described in multi-server email routing.

Common mistakes from real SES setups

  • Verifying in one region, sending in another. Identities, sandbox status and plans do not carry across regions. A "not verified" error with a verified domain is usually this.
  • Importing the whole historic list on day one. A 5% bounce rate on a single big send is enough for a review. Mail engaged contacts first.
  • No SNS subscription on the bounce topic. Events are published but nothing consumes them, so bounced addresses get mailed again next week.
  • Trusting the SES complaint rate as the full picture. Gmail complaints are not in it.
  • Staying on Essentials by accident. New accounts default to it. If you do not use the included deliverability insights, à la carte is cheaper. See Amazon SES pricing.
  • Buying a dedicated IP too early. Low or irregular volume on a dedicated IP often delivers worse than shared IPs.
  • Reusing the root account's keys. Leaked credentials are a documented cause of SES pauses. Use a least-privilege IAM identity and rotate SMTP passwords.

When Amazon SES is not a good fit

SES is the right engine for a lot of senders, but not for all of them. Choose something else if:

  • Your list is small and growing slowly. Under a few thousand contacts, a free or entry plan on an all-in-one tool may cost little or nothing and needs no DNS work at all.
  • Nobody can manage DNS and AWS. Setup is configuration rather than code, but someone must own it. If that person does not exist, you will pay in delays.
  • Your list was bought, scraped or is years old. No provider should accept it, and SES enforcement is fast. Fix the list first.
  • You need deep ecommerce integrations out of the box. Store-connected platforms sync orders and products automatically; a BYO stack needs import or API work.
  • You want a human to call. SES support runs through AWS Support plans, not an email marketing success team.

If you want an API-first provider but are not sold on AWS, compare Amazon SES vs SendGrid and Amazon SES vs Mailgun, or see our shortlist of the best SMTP service for bulk email. Many teams end up using two providers, which is easy on a BYO platform.

Frequently asked questions

Is Amazon SES good for email marketing?

For opt-in lists of several thousand contacts or more, yes: delivery is inexpensive, shared IPs are well managed, and AWS explicitly supports a Marketing mail type. It is a poor fit if you need an all-in-one tool with no setup, or if your list quality is uncertain.

Can I send newsletters directly from the SES console?

Only test messages. The console has a "Send test email" option for one recipient at a time. Bulk newsletters need the API, SMTP, or a tool that uses one of them.

How long does it take to start sending marketing email with SES?

Plan on about a week before your first real campaign: a day for DNS, up to 96 hours for AWS's initial response to the production access request, then testing. Warming up to a large list takes another two to three weeks.

Does SES handle unsubscribes automatically?

Only if you use SES subscription management with a contact list and the {{amazonSESUnsubscribeUrl}} placeholder. Otherwise your marketing tool must add the unsubscribe link and headers and stop mailing people who opt out.

Can I use SES for cold email?

Not for unsolicited bulk outreach. The AWS Acceptable Use Policy prohibits unsolicited mass email, and recipients who never asked for your mail generate the complaints that trigger reviews and pauses.

Amazon SES email marketing works best when you treat SES as the delivery layer and choose the layer above it deliberately: code for in-house engineering teams, a self-hosted app for people who like running servers, or a managed BYO platform for marketers who want to work in a browser. Get the domain verified, explain your opt-in honestly when AWS asks about your production access request, wire bounces and complaints before the first send, and warm up with your best contacts. Do that, and you get large-list email for a delivery bill measured in tens of dollars instead of hundreds.