Amazon SES is a strong choice when you need reliable, pay-as-you-go email sending and have engineers to run it. Its features are deep on the sending side: SMTP and API sending, DKIM, SPF and DMARC support, an account-level suppression list, deliverability insights and inbound mail processing. The cons all come from the same place: SES is infrastructure, not a marketing tool. New accounts start in a sandbox, enforcement on bounces and complaints is strict, and there is no campaign editor, segment builder or journey canvas, so marketing teams usually run SES underneath a platform rather than on its own.
Last updated: 6 November 2026. Every limit and threshold below was checked against AWS’s current SES documentation, linked inline. If you first need the basics, start with what Amazon SES is and how it works; this page is the review.
Amazon SES review: the short version
| Pros | Cons | |
|---|---|---|
| Cost model | Pay for volume sent and received, no upfront commitment | Extras such as dedicated IPs, attachments and deliverability add-ons are billed separately |
| Getting started | Console wizard, SMTP credentials and SDKs in most languages | Sandbox until AWS approves production access, per AWS Region |
| Deliverability | Easy DKIM, suppression list, reputation metrics, Virtual Deliverability Manager | Account review at a 5% bounce or 0.1% complaint rate |
| Marketing work | List management with topics and unsubscribe links via the API | No campaign editor, segments, journeys or marketer-facing reports |
| Who runs it | Engineers get full control of sending | Someone has to own bounce, complaint and quota handling every day |
Amazon SES features
These are the features AWS documents for SES today. The SES developer guide describes it as an email platform for sending and receiving email from your own addresses and domains, covering marketing email, transactional email such as order confirmations, and other correspondence such as newsletters.
| Feature | What you get | What to know |
|---|---|---|
| Sending interfaces | SMTP interface, SES API v2 and AWS SDKs | The API and SMTP accept messages up to 40 MB; the older v1 API stops at 10 MB |
| Templates | Stored templates with replacement tags | 20,000 templates per Region, 500 KB each, 50 destinations per templated send |
| Authentication | Easy DKIM, SPF and DMARC support for your domains | You publish the DNS records; SES verifies them |
| Suppression list | Hard bounces and complaints are suppressed at account level | On by default for accounts created after 25 November 2019 |
| List management | One contact list with topics, plus SES-inserted unsubscribe links | One contact list per account and up to 20 topics |
| Deliverability insights | Virtual Deliverability Manager dashboard and advisor | Global deliverability (inbox placement, blocklist monitoring) is a separate tier |
| Dedicated IPs | Standard dedicated IPs, managed dedicated IPs or your own IPs | With managed IPs, SES handles warm-up and scaling for you |
| Receiving email | Receipt rules that store mail in S3, call Lambda or publish to SNS | Optional KMS encryption for mail stored in S3 |
| Event publishing | Send, delivery, bounce, complaint and other events to CloudWatch or Data Firehose | Firehose can land events in Redshift, OpenSearch or S3 |
| Testing | Mailbox simulator for success, bounce, complaint and auto-reply scenarios | Simulator sends skip your quota and reputation metrics but are billed |
Limits in the table come from the SES service quotas page, the suppression list guide, the list management guide, the Virtual Deliverability Manager guide and the mailbox simulator guide.
Pros of Amazon SES
You pay for what you send, with no contract
AWS’s SES pricing page describes a pay-as-you-go model based on email volume, with no contract negotiations or upfront commitments. You can stay à la carte or pick one of three plans: Essentials, Pro or Enterprise. Pro adds managed dedicated IPs, email validation and global deliverability; Enterprise adds global endpoints and tenants for isolating reputation across workloads. We keep the actual figures in one place, our Amazon SES pricing guide, so this review does not go out of date.
It fits whatever your developers already use
Applications can send through SMTP, which suits existing mail servers and plugins, or through the API and SDKs, which give finer control and fewer network round trips. Bounce, complaint and delivery notifications go to Amazon SNS, and sending events can stream to CloudWatch or Data Firehose for your own reporting.
The reputation tooling is solid
SES supports SPF, DKIM and DMARC, with Easy DKIM to generate the DKIM keys, and the account-level suppression list and reputation metrics are built in. Virtual Deliverability Manager adds a dashboard by ISP, identity and configuration set, and an advisor that flags configuration problems. If you want the habits that keep these numbers healthy, our AWS SES dos and don’ts covers them.
It receives email too
Few sending services also process inbound mail. SES receipt rules can drop incoming messages into S3, trigger a Lambda function or publish to SNS, which is how teams build autoresponders, unsubscribe-by-reply handling or support tickets from email.
It scales without you running mail servers
You don’t manage mail servers, network configuration or IP reputation. Production quotas are set per account and per use case, and you can ask AWS to raise them as your sending grows.
Form not loading? Open it on our site.
Cons of Amazon SES
The sandbox, and a review before you can send to customers
Every new account starts in the SES sandbox: you can send only to verified addresses or the mailbox simulator, up to 200 messages in 24 hours and one message per second. Sandbox status is separate for each AWS Region, so moving to a new Region means another request. AWS gives an initial response to a production access request within 96 hours, and it can take longer if they need more information. Our guide to getting AWS SES production access covers what to put in the request.
Enforcement is strict, and it is automatic
AWS’s sending review FAQ spells out the thresholds. A bounce rate of 5% or more puts the account under review, and 10% or more can pause sending. For complaints, the lines are 0.1% for review and 0.5% for a possible pause. AWS recommends staying below 2% bounces and 0.1% complaints. A pause stops every email from the account, transactional mail included, which is why an AWS account suspension hurts more than a bad campaign.
No marketing layer
SES sends what your code gives it. There is no campaign editor, no segment builder, no journey or automation canvas and no reporting a marketer would recognise beyond delivery events. Templates are HTML and text with replacement tags. Teams that need welcome series, abandoned cart flows or A/B tests either build them or add a platform on top.
List management is thin
SES now stores contacts and topic preferences, but an account gets one contact list with up to 20 topics. That works for a product newsletter. It does not replace a customer database with segments, purchase history and consent across channels.
You own bounce and complaint handling
SES suppresses addresses, but the rest is your job: subscribing to notifications, removing bad addresses from your own systems, watching quotas and replying to AWS support cases. Each sender identity must be verified, and per-Region quotas and credentials add work for teams sending from more than one Region.
The SES numbers that mislead teams
Most reviews stop at the thresholds. The part that catches teams out is how SES measures them.
You can’t recompute your bounce rate from CloudWatch. SES counts only hard bounces to domains you haven’t verified, and it measures over a “representative volume” rather than a fixed time window. A dashboard that divides Bounce by Send for last week will not match what AWS uses to review you. Watch the Reputation.BounceRate and Reputation.ComplaintRate metrics instead, and set CloudWatch alarms on them well below 5% and 0.1%.
Gmail complaints never reach SES. The complaint rate only includes providers that send feedback loop reports, and AWS’s suppression list guide notes that Gmail doesn’t provide complaint data to SES. A Gmail user who clicks Spam is not added to your suppression list. A healthy SES complaint rate can sit alongside a poor reputation at Gmail, so watch Gmail separately and stop mailing people who never open.
An account-level pause has no event. SES does not emit an EventBridge event when it pauses or reinstates sending for the whole account. If your systems need to react, poll GetAccount and read EnforcementStatus. Don’t use SendingEnabled: it reflects only whether you switched sending off yourself, so it misses an enforcement pause.
Simulator tests are billed. Mailbox simulator sends don’t touch your quota or reputation, which makes them safe for load tests, but AWS bills them like any other email.
Is Amazon SES right for your team?
| Your situation | SES on its own | SES under a marketing platform |
|---|---|---|
| Password resets, OTPs and receipts from your app | Good fit | Optional |
| Weekly newsletter to an opted-in list | Workable with list management and topics | Easier for non-developers |
| Segmented campaigns, journeys and A/B tests | You build and maintain them | Good fit |
| Email plus WhatsApp and SMS for the same customer | SES covers email only | Good fit |
| No engineer owns email day to day | Risky: nobody watches reputation | Good fit |
Comparing SES with a full email marketing tool? Our AWS SES vs Mailchimp comparison walks through that choice, and the list of email marketing tools with AWS SES integration shows the platforms that send through your own SES account.
Where CampaignHQ fits
This is CampaignHQ’s blog, and our email runs on Amazon SES, so weigh this section with that in mind.
CampaignHQ is an AWS Partner. You can connect your own AWS account so email sends through your SES and reputation stays on your IPs, or use managed sending. On top of SES it adds what SES leaves out: email, WhatsApp and SMS on one contact database, segments, journeys, a shared team inbox and revenue attribution. Deliverability tools guide SPF, DKIM and DMARC setup and track bounces and complaints as you scale. CampaignHQ is SOC 2 Type II certified and a Meta Business Partner on the official WhatsApp Business API, and there is a 7-day free trial with no credit card.
Amazon SES FAQs
Is Amazon SES any good?
Yes, for sending. It is reliable, pay-as-you-go email infrastructure with strong authentication and reputation tools. It is a weaker fit if you want a ready-made marketing tool, because it has no campaign editor, segments or journeys.
What are the main features of Amazon SES?
SMTP and API sending, stored templates, Easy DKIM with SPF and DMARC support, an account-level suppression list, list management with topics, Virtual Deliverability Manager, dedicated IP options, inbound email processing, event publishing to CloudWatch or Data Firehose, and a mailbox simulator for testing.
What is the biggest disadvantage of Amazon SES?
It needs engineering ownership. Someone has to get out of the sandbox, handle bounces and complaints, watch reputation metrics and build any marketing workflow, because SES only sends. Strict enforcement means a neglected account can be paused, which stops transactional mail too.
How long does it take to get out of the SES sandbox?
AWS gives an initial response to a production access request within 96 hours, and approval can take longer if they ask for more details. Verifying your sending domain first helps. The request is per Region. See how to set up an Amazon SES account for the full setup.
Can marketers use Amazon SES without developers?
Not comfortably on its own. Setup needs DNS records, credentials and notification handling, and SES has no marketer-facing interface for campaigns. Marketing teams usually connect SES to an email platform that provides the editor, segments, automation and reporting.
Prefer to talk first? See how it works, or start a 7-day free trial, no credit card needed.
