How to send bulk email with Amazon SES

Can SES Do Bulk?

Yes — SES is built for volume. The catch is everything around it.

The direct answer: Amazon SES can absolutely send bulk and marketing email. There's no rule against newsletters or promotions — SES powers some of the highest-volume senders on the internet, and AWS explicitly supports marketing mail as long as recipients opted in. It even has a dedicated bulk API, SendBulkEmail, that takes a template and up to 50 recipients per call.

The reason people ask is that SES looks nothing like Mailchimp. It's a sending API: no campaign editor, no audience dashboard, no unsubscribe page, no open-rate chart. Those are all things you build on top — this guide covers each one. What you get in exchange is the price:

SES pricing as of July 2026: $0.10 per 1,000 emails sent, plus data charges for attachments. Platform prices vary by list size and features — see our full SES pricing breakdown for the detailed comparison.

Prerequisites

Before your first bulk send

Three things have to be true before a bulk campaign leaves your account. Skip any of them and the send either fails outright or lands in spam.

One more, if your account is new to volume: warm up before the big send. An account that has never delivered 50,000 messages and suddenly does looks compromised to every mailbox provider. Ramp daily volume gradually over one to two weeks, starting with your most engaged recipients — their opens and low complaint rates build the reputation that carries the rest of the list.

The Two Send Paths

SendBulkEmail vs. looping SendEmail

SES gives you two ways to send the same campaign, and the right choice depends mostly on volume.

Templates. SES templates are stored server-side (via CreateEmailTemplate) and use Handlebars-style variables — {{first_name}}, {{#if plan}}…{{/if}} — in the subject and both HTML and text bodies. At send time you supply template data as a JSON string: a default set for the whole call, plus per-recipient replacement data that overrides it. That's the entire personalization model.

A SendBulkEmail call (SES v2 API) looks like this, as of July 2026:

{
  "FromEmailAddress": "news@mail.example.com",
  "DefaultContent": {
    "Template": {
      "TemplateName": "july-newsletter",
      "TemplateData": "{\"first_name\":\"there\"}"
    }
  },
  "BulkEmailEntries": [
    {
      "Destination": { "ToAddresses": ["ada@example.com"] },
      "ReplacementEmailContent": {
        "ReplacementTemplate": {
          "ReplacementTemplateData": "{\"first_name\":\"Ada\"}"
        }
      }
    }
    // ...up to 50 entries per call
  ],
  "ConfigurationSetName": "campaign-events"
}

Note the ConfigurationSetName — it's optional, but without it you get no per-campaign event data. More on that in Measuring Results.

Compliance

Unsubscribe, consent, and the Gmail/Yahoo rules

Bulk senders face requirements that transactional senders don't, and since 2024 Gmail and Yahoo enforce them technically — not just in policy documents. As of July 2026, senders above roughly 5,000 messages per day to those providers must meet all of the following, and SES does none of it for you on ordinary API sends.

The SES suppression list. SES maintains an account-level suppression list that automatically catches hard bounces and complaints — addresses on it are dropped before sending, protecting your reputation. But it is not an unsubscribe system: someone who clicks unsubscribe never appears on it. You need your own suppression store for opt-outs, checked on every send, on top of what SES suppresses for you.

List Management

What SES gives you for lists: almost nothing

SES does have a built-in contact-list feature, and it's worth knowing exactly how minimal it is. As of July 2026 you get one contact list per account, with contacts organized into basic topics (think: "newsletter", "product updates") that recipients can opt in and out of. It can store contacts and their topic preferences. That's the feature.

What it doesn't have is everything a marketing tool means by list management: no segmentation engine (no "customers on the Pro plan who signed up this quarter"), no engagement filtering (no "exclude anyone who hasn't opened in 90 days" — SES doesn't even aggregate opens per contact), no custom fields beyond what you serialize yourself, no import/export tooling, no preference center UI. Sending to a segment means your application queries its own database for the audience, applies its own suppression and engagement rules, and hands SES the final address list.

In practice, teams doing bulk on SES keep the audience in their own database or bring a tool that manages it for them. The contact list is fine as a bare opt-in/opt-out store; it is not a CRM and doesn't try to be.

Throughput

Pushing a big campaign through a rate limit

Your sending rate — commonly around 14 messages per second for newer production accounts — is the bottleneck for any large campaign, and SES enforces it hard: exceed it and calls fail with a Throttling error. SES doesn't queue anything for you, so the campaign pipeline is yours to engineer.

Measuring Results

Knowing what actually happened to the send

A successful API call means SES accepted the message — nothing more. Deliveries, bounces, complaints, opens, and clicks arrive later as events, and you only get them if you set up a configuration set with an event destination (SNS, Kinesis Firehose, EventBridge, or CloudWatch) and attach it to the send.

Even then, what you receive is a stream of individual events, not a campaign report. To answer "how did Tuesday's newsletter do?" you need to tag each send with a campaign identifier (message tags on the configuration set, or the config set name itself), consume the event stream, and aggregate per campaign yourself — deliveries over sends, bounce rate, complaint rate, opens and clicks if you enabled tracking. There is no SES dashboard that shows results per campaign.

Two numbers matter beyond curiosity: bounce rate and complaint rate feed your SES account reputation, and a single bulk send to a stale list can push you over the review thresholds. Wire the event stream into your suppression store — hard bounces and complaints from this campaign must be excluded from the next one automatically.

SendOps

The honest math — and the shortcut

SES can absolutely do bulk email at $0.10 per 1,000. But tally what this guide just described: audience storage and segmentation, consent and suppression tracking, RFC 8058 headers and an unsubscribe endpoint, a template system, a queue with pacing and backoff, an event pipeline, and per-campaign aggregation. Everything around the send is yours to build. That's a reasonable project for a team that wants to own it — and a lot of undifferentiated plumbing for everyone else.

SendOps is that layer, running through your own SES account — your quota, your reputation, SES's pricing: