Amazon SES

Name: Amazon SES
Brand: Amazon SES
Price: 0.101000 USD

The cheapest way to send email, and the most work

Amazon Simple Email Service is AWS's transactional email infrastructure, an API and SMTP endpoint for sending application email such as receipts, password resets, and notifications at roughly $0.10 per 1,000 messages a la carte, with inbound receiving through Mail Manager; it is the price floor the whole category is measured against, and it is raw infrastructure rather than a product, with no campaign builder, no list management, and only a rudimentary console.

Visit website

Overview

Amazon SES launched in 2011 as the sending infrastructure behind Amazon's own email, opened up to AWS customers. Fifteen years later it is still the same proposition: enormous, reliable sending capacity at a price no commercial provider can match, wrapped in almost nothing. There is no template designer worth the name, no searchable message log showing what you actually sent, no marketing tooling, and no support relationship unless you buy an AWS support plan separately. What you get is an endpoint that accepts email and delivers it, at $0.10 per 1,000 messages on the a la carte rate.

That price is the entire argument. Sending a million messages a month costs about $100 on SES against roughly $650 on Resend, $1,200 or more on Postmark's overage arithmetic, and a negotiated figure at SendGrid. For a business at genuine volume the annual difference runs into tens of thousands of dollars, which is why almost every high-volume sender eventually evaluates SES and many end up there.

The costs are real and they are not on the invoice. Every new account starts in a sandbox that only sends to verified addresses, and you must request production access, which AWS reviews and usually answers in one to three business days. Reputation is policed hard: a bounce rate above 5 percent puts your account under review, above 10 percent pauses it, and a complaint rate above 0.01 percent pauses it too. There is no vendor vetting your neighbours on shared infrastructure, so your own hygiene is the whole defence. And when something goes wrong, the diagnostic tooling is CloudWatch metrics and event streams you configure yourself, not a searchable list of messages.

In 2025 AWS restructured SES into named pricing plans, Essentials, Pro, and Enterprise, layered above the original a la carte rate, with monthly minimums of $105 for Pro and $500 for Enterprise per account per region. For a small business the a la carte and Essentials paths remain the relevant ones, and they are self-serve without a sales conversation. Mail Manager handles inbound at $0.10 to $0.15 per 1,000 messages depending on the operation, and Virtual Deliverability Manager adds reputation reporting as a metered extra.

Best for

Engineering teams already running on AWS that send high transactional volume, have the capability to build their own bounce handling, suppression, and log storage, and want the lowest possible per-message cost.

Not the right fit for

Anyone who wants an email marketing platform; SES has no campaign builder, no list management, no segmentation, no automation, and no signup forms, and pointing a marketing tool at SES as a relay is a separate architecture decision with its own risks.
Small teams without engineering capacity to build around it; bounce processing, suppression, log storage, and template management are all your responsibility, and getting any of them wrong gets the account paused.
Cold outreach and purchased-list senders; a complaint rate above 0.01 percent pauses your account, which cold lists will breach almost immediately, and a paused SES account also takes down your legitimate transactional mail.
Businesses that need someone to call when email stops arriving; SES support means an AWS support plan you buy separately, and the base tier does not include technical help.
Low-volume senders optimising for total cost including time; below a hundred thousand messages a month the saving against Resend or Postmark is tens of dollars and the engineering overhead costs more than that.

How it works

1
You verify a sending identity, either a single email address or a whole domain, by publishing DKIM CNAME records and optionally a custom MAIL FROM subdomain for SPF alignment. Domain verification is the correct path for anything real; address verification is for testing.
2
New accounts sit in a sandbox that will only send to verified recipients, with a low daily quota. You raise a production access request through Service Quotas in the SES console, describing what you intend to send and how you handle bounces and unsubscribes. AWS typically responds within one to three business days and does reject applications that read as bulk marketing.
3
Your application sends through the SES v2 API using any AWS SDK, or through the SMTP interface using credentials generated from an IAM user. Because it is an AWS service, permissions are IAM policies, which is either a benefit or an obstacle depending on how your organisation works.
4
Delivery outcomes do not appear in a console log. You configure a configuration set with an event destination that publishes sends, deliveries, bounces, complaints, opens, and clicks to SNS, Kinesis Firehose, CloudWatch, or EventBridge, and you are responsible for storing and querying them. Bounce and complaint handling is your code's job: SES will suspend you for a bad rate, it will not clean your list for you.
5
For inbound, Mail Manager accepts mail at MX records you point at SES and applies rule sets that can deliver to S3, invoke Lambda, publish to SNS, or apply archiving and traffic policies. It delivers raw MIME rather than parsed JSON, so parsing is your code's problem.

Feature breakdown

26 features in 5 modules

Sending

Raw capacity, exposed through AWS's normal interfaces.

SES v2 API: Send simple, raw MIME, templated, or bulk-templated messages through any AWS SDK, with IAM-based authentication rather than API keys.
SMTP interface: Standard SMTP endpoint per region with credentials derived from an IAM user, so any framework mailer or legacy application can relay through SES.
AWS SDK coverage: Every language AWS supports has an SDK, which in practice is broader coverage than any commercial email vendor offers.
Bulk templated sending: Send one template to many recipients with per-recipient replacement data in a single call, which is the closest SES comes to a campaign send.
Configuration sets: Named groups of sending settings that control which IP pool is used, which events are published where, and which reputation and suppression options apply, so different traffic types can be isolated.
Account-level and configuration-set suppression: SES maintains a suppression list of addresses that hard bounced or complained, either at account level or per configuration set, which you can read and modify through the API.

Deliverability infrastructure

Powerful, and entirely your responsibility to operate.

Easy DKIM and custom MAIL FROM: SES generates DKIM CNAME records for domain verification and supports a custom MAIL FROM subdomain so SPF aligns for DMARC.
Dedicated IPs, standard and managed: Standard and bring-your-own IPs are priced at about $24.95 per IP per month, while Managed Dedicated IPs start around $15 per month plus a small per-email fee and handle warmup automatically, which is the only version most small businesses should consider.
Reputation metrics dashboard: Account-level bounce and complaint rates with status indicators, plus per-configuration-set reputation tracking so one traffic type's problems can be isolated.
Virtual Deliverability Manager: A metered add-on from roughly $0.07 per 1,000 emails that adds engagement and deliverability insights, ISP-level placement reporting, and guided recommendations. Not included by default.
Mailbox simulator: Special addresses that simulate bounces, complaints, and out-of-office replies so you can test your handling code without damaging your reputation.
Sending quotas and rate limits: Every account has a daily sending quota and a per-second rate limit, raised automatically as you send well or manually by request. Exceeding them returns throttling errors rather than a bill.

Inbound with Mail Manager

Real inbound capability, delivered raw.

Rule sets for incoming mail: Point MX records at SES and define ordered rules that match on recipient and act, giving flexible routing similar in spirit to Mailgun's routes.
Delivery to S3, Lambda, SNS, or EventBridge: Incoming messages can be stored, processed by your own function, or published as events, which suits pipelines rather than webhooks.
Archiving and traffic policies: Mail Manager adds retained archives with search and traffic policies that block or allow mail before it reaches your handlers.
Raw MIME rather than parsed JSON: SES hands you the original message, so extracting the reply text, stripping quoted history, and decoding attachments are your code's job. Postmark and Mailgun do that for you.
Metered inbound pricing: Inbound email is charged around $0.10 per 1,000 messages, with Mail Manager email processing around $0.15 per 1,000 and incoming chunks around $0.09 per 1,000.

Observability

Build-it-yourself, which is the single biggest hidden cost.

Event publishing: Sends, deliveries, bounces, complaints, rejects, opens, clicks, delivery delays, and subscriptions can be published to SNS, Kinesis Firehose, CloudWatch, or EventBridge from a configuration set.
CloudWatch metrics: Aggregate sending, bounce, and complaint metrics with alarms, which is how you find out about a reputation problem before AWS emails you about it.
No searchable message log: SES does not keep a browsable list of the messages you sent with their content. If you want to answer what did we send this customer three weeks ago, you have to have stored it yourself.
Message archiving through Mail Manager: Mail Manager can archive messages with search and configurable retention, which is the nearest thing SES offers to a commercial provider's activity log, and it is a separate metered service.

AWS platform integration

Where SES stops looking expensive in engineering time.

IAM permissions: Sending permissions are IAM policies, so email access is governed by the same identity system as the rest of your infrastructure with no separate API key sprawl.
Multi-region: SES runs in most AWS regions, so European buyers can send from an EU region and keep processing there, with each region carrying its own reputation and quotas.
VPC endpoints and PrivateLink: Send from private subnets without traversing the public internet, which some regulated environments require.
CloudFormation and Terraform support: Identities, configuration sets, and event destinations are all declarable as infrastructure code alongside everything else.
AWS billing consolidation: Email appears on the existing AWS invoice with the same tagging, cost allocation, and committed-spend arrangements as the rest of the account.

Use cases

4 documented

High-volume platform whose email bill became a line item

Three million notifications a month cost several thousand dollars at a commercial provider and finance has started asking about it.

Moving to SES cuts the sending cost to roughly $300 a month. The team spends two weeks building bounce processing, event storage, and dashboards, and the payback is the first month.

Engineering team already deep in AWS

Everything runs on Lambda and SQS, secrets are in IAM, and adding another vendor means another key, another SOC 2 review, and another invoice.

SES sends from the same IAM identities, publishes events to the same EventBridge bus, and appears on the same bill, so the operational surface does not grow at all.

Marketing platform builder needing wholesale sending

A product that sends on behalf of its own customers needs sending capacity at wholesale cost, with per-tenant isolation and no vendor markup.

Configuration sets isolate each tenant's reputation, managed dedicated IPs separate the traffic that warrants it, and the per-message cost is low enough that the product can resell sending profitably.

European buyer with data residency requirements

Procurement requires that customer email content be processed and stored within the EU, and most commercial providers offer no regional guarantee.

SES runs in EU regions with the whole processing path, event storage, and archives kept there, backed by AWS's standard compliance documentation.

Pricing

from $0.10 per 1,000 emails a la carte

Pay-as-you-go metered infrastructure charged per 1,000 messages, plus separate meters for data transfer, dedicated IPs, deliverability tooling, and inbound. Named pricing plans (Essentials, Pro, Enterprise) sit above the a la carte rate with monthly minimums on the upper two.

Plan	Price	Includes
A la carte	$0.10 per 1,000 outbound emails	No monthly minimum Full API and SMTP access Configuration sets, event publishing, and suppression included Deliverability tooling and dedicated IPs charged separately The rate everyone quotes and the right choice for almost every small business on SES.
Essentials	$0.16 per 1,000 emails up to 10 million, falling to $0.14 and $0.11 at higher volume	No monthly minimum Bundles additional deliverability features above the a la carte path Volume discounts as sending grows
Pro	$0.22 per 1,000 emails up to 10 million, with a $105 monthly minimum per account per region	$0.17 per 1,000 from 10 to 100 million $0.12 per 1,000 above 100 million Higher included deliverability capability The $105 monthly minimum makes this irrelevant below roughly half a million messages a month.
Enterprise	$0.23 per 1,000 emails up to 10 million, with a $500 monthly minimum per account per region	$0.18 per 1,000 from 10 to 100 million $0.13 per 1,000 above 100 million Highest included support and deliverability capability

Add-ons

Data and attachments ($0.12 per GB): Charged on the size of what you send, so image-heavy or attachment-heavy mail costs more than the headline rate implies.
Managed Dedicated IP (From about $15 per month plus $0.02 to $0.08 per 1,000 emails): Handles warmup automatically; the only dedicated IP option most small businesses should consider.
Standard or bring-your-own dedicated IP (About $24.95 per IP per month): Bring-your-own IP ranges carry a minimum block size that makes them enterprise-only.
Virtual Deliverability Manager (From about $0.07 per 1,000 emails plus query fees): Adds engagement and placement insights; not included by default.
Inbound email and Mail Manager (About $0.10 per 1,000 inbound emails, $0.15 per 1,000 processed, $0.09 per 1,000 chunks)

Billing notes

SES bills per message sent, not per contact stored, so dormant and unsubscribed contacts cost nothing. There is no list living in SES at all; your contacts live in your own database.
The headline $0.10 per 1,000 rate excludes data transfer at $0.12 per GB, which matters for mail with images or attachments, and excludes every deliverability add-on.
There is no overage concept because there is no included allowance. What limits you is the account sending quota and per-second rate limit, and exceeding those returns throttling errors rather than charges.
The Pro and Enterprise plans carry monthly minimums of $105 and $500 per account per region, which are irrelevant at small-business volume; stay on a la carte or Essentials.
The old SES free tier of 3,000 message charges a month for 12 months is no longer available to new customers, so plan on paying from message one, albeit a very small amount.
Support is not included. AWS technical support is a separate subscription, and the base support plan does not cover help with deliverability problems.
Every region is a separate account for reputation, quota, and billing purposes, so multi-region sending means multi-region reputation management.

Value assessment: The arithmetic is brutal in SES's favour and misleading at small scale. A product with 1,000 users receiving three emails each sends 3,000 messages a month and pays about 30 cents. Ten thousand users at three emails each is 30,000 sends, about $3. Fifty thousand users at three emails each is 150,000 sends, about $15, against roughly $80 on Resend, $145 on Mailgun, and $199 on Postmark. At a million messages a month SES is around $100 against $650 on Resend. Nothing in the category competes on price. But the comparison is not like for like: the $65 you save each month at 150,000 messages buys you nothing on SES that resembles a searchable log, a template editor, sender vetting, or a support relationship, and building the missing pieces is a week or two of engineering plus permanent maintenance. The honest threshold is somewhere around half a million messages a month, or wherever your team already has the AWS operational muscle. Below that, SES is cheap for the same reason a bag of flour is cheaper than bread.

Strengths & limitations

Strengths

By far the lowest per-message cost in the category at $0.10 per 1,000 a la carte, roughly five to twenty times cheaper than the commercial providers.
Effectively unlimited sending capacity backed by AWS's infrastructure, with quotas that scale as you demonstrate good sending behaviour.
Deep AWS integration: IAM permissions, EventBridge and SNS event publishing, CloudWatch alarms, VPC endpoints, CloudFormation and Terraform support, and consolidated billing.
Multi-region availability including EU regions, giving genuine data residency control that most commercial providers do not offer on self-serve plans.
Configuration sets provide real reputation isolation between traffic types, which is more granular than most vendors' subaccount models.
Managed Dedicated IPs handle warmup automatically from about $15 a month, which is far cheaper than commercial providers' $30 to $59 dedicated IP charges.
Mail Manager gives genuine inbound capability with rule sets, archiving, and traffic policies, delivering to S3, Lambda, SNS, or EventBridge.
Fifteen years of operation as core AWS infrastructure, which is the lowest vendor risk in this entire category.

Limitations

No searchable message log. You cannot open the console and read what you sent a customer three weeks ago unless you built the storage yourself, which is the single most jarring difference from every commercial provider.
Reputation policing is unforgiving and automated: a bounce rate above 5 percent puts the account under review, above 10 percent pauses it, and a complaint rate above 0.01 percent pauses it. A pause takes down all your transactional mail at once.
Production access requires an application that AWS reviews over one to three business days and can reject, so SES is not a same-hour decision.
Support is a separate AWS subscription, and there is nobody vetting your neighbours on shared infrastructure the way Postmark does.
No marketing capability at all: no campaigns, no lists, no segmentation, no automation, no forms, and no meaningful template designer.
Bounce handling, complaint processing, suppression synchronisation, and log retention are all engineering work you own permanently, not just at setup.
The 2025 move to named pricing plans with $105 and $500 monthly minimums added complexity to what used to be the simplest price in the category.
Inbound delivers raw MIME, so reply-text stripping and attachment handling are your code's problem where Postmark and Mailgun hand you parsed JSON.

Head-to-head comparisons

5 alternatives

Amazon SES vs Resend

from $0 for 3,000 emails a month, then $20 a month for 50,000 emails

SES is about five times cheaper at 150,000 messages a month ($15 against roughly $80) and the gap widens with volume. Resend gives you a searchable 30-day log, guided DKIM setup, thirteen first-party SDKs, React Email, and support that answers, none of which SES has. Below roughly half a million messages a month the absolute saving is smaller than the engineering time SES demands, so most small software businesses should be on Resend. Above it, the arithmetic flips hard.

Full Amazon SES vs Resend comparison

Amazon SES vs Postmark

from $15 a month for 10,000 emails (Basic)

The widest gap in the category: SES costs roughly fifteen to twenty times less per message. Postmark's premium buys sender vetting that keeps its shared IP pools clean, full message content searchable for up to 365 days, parsed inbound with reply-text stripping, and support on every plan. SES gives you none of that and will pause your account if complaints exceed 0.01 percent. If a failed password reset is a business incident and you send under a few hundred thousand messages a month, Postmark is the better buy despite the price.

Full Amazon SES vs Postmark comparison

Amazon SES vs Twilio SendGrid

from $15 a month (Marketing Campaigns Basic) or $19.95 a month (Email API Essentials)

SendGrid is the middle ground and many teams move from it to SES once volume makes the bill visible. SendGrid gives you templates, an activity feed, marketing campaigns, address validation, and a support path, at roughly ten times the per-message cost. SES gives you the wholesale rate and expects you to build the rest. Teams already inside AWS with engineering capacity usually find SES obviously correct at scale; teams without it discover why SendGrid charges what it charges.

Full Amazon SES vs Twilio SendGrid comparison

Amazon SES vs Mailgun

from $15 a month for 10,000 emails (Basic)

Both offer real inbound, but they hand it over differently: Mailgun parses messages into JSON and routes them with rules, SES Mail Manager delivers raw MIME to S3, Lambda, or SNS with rule sets around it. Mailgun costs roughly ten to fifteen times more per message and includes address validation, a console, and human support. SES wins decisively on price and on AWS-native integration; Mailgun wins on how much work you avoid.

Full Amazon SES vs Mailgun comparison

Amazon SES vs Brevo

from $0 (free, 300 emails per day), then $9/mo on Starter at 5,000 emails

Not really comparable, but small businesses do consider both because both are cheap. Brevo is a complete marketing platform with campaigns, automation, a CRM, and a transactional API on a send-based meter, usable by a non-technical team on day one. SES is infrastructure with no marketing capability, no interface worth using, and no path for someone who is not an engineer. If you were choosing between them, you almost certainly want Brevo.

Full Amazon SES vs Brevo comparison

Implementation & onboarding

Setup time: A day of configuration plus one to three business days waiting for production access. Getting to a genuinely production-ready state, with bounce processing, suppression sync, event storage, and alarms, is realistically one to two weeks of engineering.
Learning curve: High relative to every commercial alternative, though low for anyone fluent in AWS. The email-specific concepts are straightforward; the work is in accepting that SES gives you primitives and you build the product around them.
Onboarding: Self-serve with an approval gate. There is no sales call, but the production access request is a real review that describes your sending practices, and applications that read as bulk marketing get rejected. Support is a separate AWS subscription.
Migration notes: Moving to SES from a commercial provider is not a credentials swap. Plan for building bounce and complaint handling first, because SES will suspend an account whose rates drift, and importing a suppression list from the old provider into the SES account-level suppression list before the first send is essential. Templates do not migrate and typically get rewritten. Warm up gradually: send a small share of traffic through SES for a week or two while watching CloudWatch reputation metrics, because a new SES identity has no reputation and the automated policing gives you very little margin. Keep the old provider live during the ramp so a pause does not take down your password resets.

Platform, API & security

Platforms: AWS ConsoleSES v2 API through every AWS SDKSMTP interfaceMail Manager for inboundCloudFormation and Terraform
API: SES v2 API accessible through every AWS SDK with IAM authentication, covering simple, raw MIME, templated, and bulk-templated sending, identity and DKIM management, configuration sets, suppression lists, dedicated IP pools, and account details. An SMTP interface is available per region with IAM-derived credentials. Events publish to SNS, Kinesis Firehose, CloudWatch, or EventBridge rather than to HTTP webhooks, so consuming them means an AWS-side pipeline.
Compliance: SOC 1, 2, and 3ISO 27001, 27017, 27018PCI DSSHIPAA-eligible under a BAAGDPR with the AWS data processing addendumFedRAMP in relevant regions
Data residency: Available in most AWS regions including several in the EU. Each region is independent for reputation, quota, and billing, and choosing an EU region keeps the processing path and any archives there.
SSO: Handled by AWS IAM Identity Center rather than by SES itself, which means SSO comes free with the rest of your AWS access management.
Security notes: IAM policies govern who can send and from which identity, VPC endpoints and PrivateLink allow sending without traversing the public internet, and CloudTrail records API activity. SES itself stores no message bodies, which is good for data minimisation and is exactly why there is no searchable log of what you sent.

Support & resources

Channels: AWS Support plans purchased separatelyAWS re:Post communityService Quotas requests for limits and production access
Documentation: Extensive documentation in the Amazon SES Developer Guide covering identities, sending, event publishing, dedicated IPs, deliverability, and Mail Manager, plus the AWS Messaging and Targeting blog.
Community: AWS re:Post, Stack Overflow, and a very large body of third-party tutorials, which is often the fastest route to an answer given the absence of included vendor support.

Company

Founded: 2011
Headquarters: Seattle, Washington, United States
Ownership: Amazon Web Services, a subsidiary of Amazon.com Inc (NASDAQ: AMZN)
Employees: Part of Amazon Web Services, itself part of Amazon (over 1.5 million employees group-wide)
Funding: Not applicable; SES is a service of a publicly listed company and has never been separately funded.

Timeline

2011Amazon SES launches, exposing the sending infrastructure behind Amazon's own email to AWS customers.
2015Adds inbound email receiving with rule sets delivering to S3, Lambda, and SNS.
2019Introduces the reputation dashboard and account-level suppression list, formalising the automated bounce and complaint policing that governs every account.
2022Ships the SES v2 API and Virtual Deliverability Manager, adding engagement and placement insights as a metered add-on.
2024Launches Mail Manager, a more capable inbound layer with rule sets, archiving with search, and traffic policies.
2025Restructures pricing into named Essentials, Pro, and Enterprise plans above the a la carte rate, and withdraws the SES-specific free tier for new customers.

Integrations

Every AWS SDK language
Rails, Django, Laravel, and other framework mailers via SMTP
AWS Lambda, EventBridge, SNS, SQS, Kinesis Firehose, and CloudWatch
Amazon S3 for inbound message storage
CloudFormation, Terraform, and CDK
WordPress via SMTP plugins
Open-source newsletter tools such as Listmonk that relay through SES
Self-hosted marketing platforms using SES as a sending backend
AWS IAM Identity Center for access control
AWS CloudTrail for audit logging

Frequently asked questions

10 questions

What is Amazon SES?

Amazon SES is AWS's transactional email infrastructure. It provides an API and an SMTP endpoint for sending application email such as receipts, password resets, and notifications, plus inbound receiving through Mail Manager. It is priced per message at roughly $0.10 per 1,000 emails a la carte. It is infrastructure rather than a product: there is no campaign builder, no list management, and no searchable log of what you sent.

How much does Amazon SES cost?

The a la carte rate is $0.10 per 1,000 outbound emails, plus $0.12 per GB of data. Named plans sit above that: Essentials at $0.16 per 1,000 with no minimum, Pro at $0.22 with a $105 monthly minimum per account per region, and Enterprise at $0.23 with a $500 minimum. Inbound is around $0.10 per 1,000. Managed dedicated IPs start around $15 a month. For a small business, a la carte is the right path.

Is there still an Amazon SES free tier?

Not the SES-specific one. The historical free tier of 3,000 message charges a month for your first 12 months is no longer available to new customers. New AWS accounts receive general AWS free tier credits that can be spent on SES instead. In practice this matters little, because 3,000 emails costs about 30 cents anyway.

Can I do email marketing with Amazon SES?

Not directly. SES has no campaign builder, no contact lists, no segmentation, no automation, and no signup forms. Some businesses point a self-hosted or third-party marketing tool at SES as a sending backend, which works but makes you responsible for the list hygiene, unsubscribe handling, and complaint rates that the marketing platform would otherwise manage. Given SES pauses accounts above a 0.01 percent complaint rate, that is a serious responsibility.

Will Amazon SES suspend my account?

Yes, and it is automated rather than negotiated. A bounce rate above 5 percent puts your account under review and above 10 percent pauses sending. A complaint rate above 0.01 percent, which is one complaint in ten thousand messages, also pauses sending. Because a pause hits your whole account, your transactional mail goes down with whatever caused the problem. This is why cold outreach on SES is a very bad idea and why bounce processing has to exist before your first real send.

Do inactive or unsubscribed contacts cost me anything on SES?

No. SES has no concept of a stored contact at all. Your list lives in your own database and SES bills only for messages sent. That removes the classic hidden cost of contact-priced marketing platforms entirely, but it also means unsubscribe handling and suppression synchronisation are code you write rather than a feature you buy.

How do I see what emails I sent on SES?

You configure it yourself. SES does not store message bodies and has no browsable activity log. You attach a configuration set with an event destination that publishes send, delivery, bounce, complaint, open, and click events to SNS, EventBridge, CloudWatch, or Kinesis Firehose, and you store and query them. Mail Manager can archive messages with search as a separate metered service. This is the biggest practical difference from every commercial provider.

How do I get out of the SES sandbox?

You submit a production access request through Service Quotas in the SES console, describing what you send, how you obtain recipients, and how you handle bounces and unsubscribes. AWS typically responds in one to three business days. Requests that read as bulk marketing or that cannot describe bounce handling do get rejected, so answer carefully and specifically.

Does SES support inbound email?

Yes, through Mail Manager. Point MX records at SES and define rule sets that deliver mail to S3, invoke a Lambda function, publish to SNS, or apply archiving and traffic policies. The important difference from Postmark and Mailgun is that SES hands you the raw MIME message, so parsing headers, separating reply text from quoted history, and decoding attachments are all your code's responsibility.

When is Amazon SES actually the right choice?

When you already run on AWS, have engineering capacity to build bounce handling and event storage, and send enough volume for the price difference to matter. Below roughly half a million messages a month, the saving against Resend or Postmark is tens of dollars while the engineering and operational burden is permanent. Above that, and especially into the millions, SES becomes hard to argue against on cost alone.

Editorial verdict

Amazon SES is the price floor of this entire category and it earns that position honestly: $0.10 per 1,000 messages, effectively unlimited capacity, EU regions for data residency, and IAM-native permissions that keep email inside the access model you already run. If you send millions of messages a month and have AWS competence in the building, the arithmetic is not close and everything else in this category looks like a markup. But SES is deliberately not a product. There is no searchable log of what you sent, no template editor worth the name, no sender vetting protecting your shared infrastructure, no support unless you buy it separately, and no marketing capability at all. Worse, the reputation policing is automated and merciless: one complaint in ten thousand messages can pause your whole account, taking your password resets down with your newsletter. For a small business under a few hundred thousand messages a month, the monthly saving against Resend or Postmark is smaller than the cost of the engineering you would have to do, and considerably smaller than the cost of one suspended account. Choose SES when volume or AWS gravity makes it obvious. Do not choose it just because it is cheap.

Written by the SaaSTracker editorial team. Awards, when shown, are judged against the published criteria in our methodology.