Amazon SES Review 2026: The Cheapest Way to Send, If They Let You
The Best: $0.10 per 1,000, and reputation thresholds published as numbers
The Worst: 31% of reviews are about the sandbox, and the old free tier is gone
The short version
Amazon SES sends email for $0.10 per thousand without a plan. Nothing else on this site is close. It is the reason a large fraction of the internet’s transactional email leaves an AWS region, and it carries over a trillion messages a year for customers Amazon names publicly: Netflix, Duolingo, and Amazon’s own retail operation including Prime Day.
Getting permission to use it is the hard part, and the corpus is dominated by that fact. Every new account starts in a sandbox that permits 200 messages per 24 hours at 1 message per second, and only to addresses you have verified. Leaving requires a request to AWS Support. 38 of the 123 reviews we read, 31 percent, discuss that gate, and their experiences do not converge. One says “Initially you are sandboxed and have to apply to have this removed manually. It’s quick, however!” Another waited a month for a customer’s account. A third was refused outright: “I didn’t get the production access and I don’t send spam … Its seems they’re very picky who can use it.”
One correction before you budget. The free tier that half the internet still quotes, 62,000 emails a month when sending from EC2, is no longer on the pricing page. We looked twice. What is there instead is up to $200 in AWS Free Tier credits, a free plan available “for 6 months after account creation”, and credits that must be used within twelve months. Four reviews in the corpus still cite the old figure. It is gone.
What you get for the price and the paperwork is the most transparent reputation system in this category. AWS publishes the exact numbers at which it acts: a bounce rate of 5 percent puts you under review, 10 percent can pause your sending; a complaint rate of 0.1 percent puts you under review, 0.5 percent can pause you. No other provider we have reviewed tells you where the line is.
If you already run on AWS and you send a lot, this is the correct answer and the cost difference is not close. If you do not, you are adopting an entire cloud platform to get a mail relay, and the interface, the credentials and the approval process will all cost you more time than the money you save.
What this review scores, and what SES is not trying to be
SES is infrastructure. It has no campaign builder, no journeys, no visual editor, and it is not apologising for any of that. Our automation category scores those things, so SES scores low there, and that number is a description rather than a criticism. Read it the way you would read “this van has no back seats”.
The categories that decide whether a relay is any good are deliverability, price and API, and that is where the interesting readings on this page are. One more framing note: SES has never appeared in the independent seedlist inbox placement panel we quote elsewhere on this site, and that panel has since stopped running. So the deliverability score here rests on published reputation policy, on scale, and on the corpus, and we say so where it matters.
SMTP settings
| Hostname pattern | email-smtp.{region}.amazonaws.com, for example email-smtp.eu-west-1.amazonaws.com |
|---|---|
| STARTTLS ports | 25, 587, 2587. AWS: “the SMTP client connects to the Amazon SES SMTP endpoint on port 25, 587, or 2587, issues an EHLO command, and waits for the server to announce that it supports the STARTTLS SMTP extension.” |
| TLS Wrapper ports | 465, 2465. AWS: “To set up a TLS Wrapper connection, the SMTP client connects to the Amazon SES SMTP endpoint on port 465 or 2465.” |
| Username | Your SES SMTP username, which matches the AWS access key ID |
| Password | A dedicated SMTP password. AWS: “Your SMTP password is different from your AWS secret access key.” It must be generated, or derived from an IAM user’s credentials. |
| FIPS endpoints | Available in us-east-1, us-east-2, us-west-1, us-west-2, ca-central-1 and both GovCloud regions, as email-smtp-fips.{region}.amazonaws.com |
| Max message size | 40 MB via SMTP or API v2. 10 MB via API v1. Both after base64 encoding. |
| Recipients per message | 50, counting To, CC and BCC together. Not adjustable. |
| API v2 send | POST /v2/email/outbound-emails |
This is the detail almost nobody publishes, and it will ruin an afternoon if you assume otherwise. AWS states: “SMTP endpoints are not currently available in Africa (Cape Town), Asia Pacific (Hyderabad), Asia Pacific (Jakarta), Europe (Milan), Europe (Zurich), Israel (Tel Aviv), Middle East (Bahrain), Middle East (UAE), Canada West (Calgary), Asia Pacific (Malaysia).” The API works in those regions. The SMTP interface does not. If your data residency requirement points at Milan or Zurich, you cannot use SMTP there.
Every hostname pattern, port, size limit and price above was read from AWS documentation twice, the second time asking only for literal text. Anything that did not appear in both passes is not on this page. One example of what that excludes: we could not find AWS documenting which SMTP AUTH mechanism it uses, so we do not say. Other sites will tell you. They are guessing.
Snapshot
| Launched | 25 January 2011, as “a highly scalable and cost-effective bulk and transactional email-sending service for businesses and developers” |
|---|---|
| Scale | “processes over a trillion email each year”, with Netflix, Duolingo and Amazon Retail named publicly |
| Base rate, no plan | $0.10 per 1,000 emails |
| Essentials plan | No monthly base fee. $0.16 per 1,000 up to 10M, $0.14 from 10 to 100M, $0.11 above 100M. |
| Pro plan | $105 per account, per region, per month, plus $0.22 / $0.17 / $0.12 per 1,000 across the same bands |
| Enterprise plan | $500 per account, per region, per month, plus $0.23 / $0.18 / $0.13 per 1,000 |
| Attachments | $0.12 per gigabyte of attachment data sent |
| Dedicated IPs | Standard $24.95 per month per IP. Managed $15 per month per account plus a per-email fee. |
| Free tier | Up to $200 in AWS Free Tier credits. A free plan “available for 6 months after account creation”. Credits expire twelve months after account creation. The old 62,000-per-month EC2 allowance is not on the pricing page. |
| Sandbox | 200 messages per 24 hours, 1 per second, only to verified addresses or the mailbox simulator. Suppression list management APIs disabled. |
| Leaving the sandbox | A production access request in the console, declaring Marketing or Transactional, a website URL, and an acknowledgement. AWS: “The AWS Support team provides an initial response to your request within 24 hours.” |
| Bounce policy | Under review at 5 percent, sending pause possible at 10 percent |
| Complaint policy | Under review at 0.1 percent, sending pause possible at 0.5 percent |
| Official MCP | No. AWS’s MCP catalogue lists 62 servers and none is SES. A sample exists and is marked not for production. |
What Amazon SES does well
It is the cheapest way to send email, by a distance
At $0.10 per thousand without a plan, a million emails a month costs $100. The nearest comparable figures in this category are several times higher, and above 100 million a month the Essentials rate falls to $0.11 per thousand with no monthly base fee at all.
The corpus reflects it more clearly than any score could. Price is raised in 15 of 123 reviews, and it is raised as a compliment nearly every time, which is the reverse of every other platform on this site. Capterra’s value for money sub-score is 4.6, the highest component score we have recorded anywhere. On HubSpot the same field sits under a corpus where 42 percent complain about cost.
The reputation rules are published as numbers
This is the thing we would most like every provider in this category to copy. AWS does not tell you to maintain good sending practices. It tells you the thresholds:
| Metric | Target | Under review at | Sending pause at |
|---|---|---|---|
| Bounce rate | below 2% | 5% | 10% |
| Complaint rate | below 0.1% | 0.1% | 0.5% |
And it defines the states rather than leaving them to inference. Under review: “We’ve detected an issue related to the email sent from your account, and we’re giving you time to fix it. You can continue to send email as you normally would.” Sending pause: “We paused your account’s ability to send email because of a critical issue.”
Set that against SendGrid, whose governing acceptable use policy contains no explicit email clause at all and where seven reviewers describe being cut off with no notice. SES will also stop you, but it tells you the number in advance and warns you before it acts.
Regional endpoints, FIPS variants, and GovCloud
SES exposes an SMTP endpoint in nineteen regions including both GovCloud partitions, with FIPS-validated variants in seven of them. For anyone with a data residency obligation or a federal compliance requirement, this is a category of capability the rest of this field does not have. Ireland, Frankfurt, London, Paris and Stockholm all work; the caveat about the ten regions without SMTP is in the box above.
Scale that is not a marketing claim
A trillion emails a year, with named customers, and Amazon’s own retail business sending Prime Day mail through it. Whatever else is true about the developer experience, the sending platform itself is not going to fall over on your launch day, and the corpus contains almost no complaints about reliability.
An honest, well-instrumented suppression model
Account-level suppression is automatic, bounces and complaints are published as events you subscribe to through Amazon SNS, and the whole thing is inspectable. It requires work to wire up, which is the next section’s problem, but nothing is hidden from you once it is.
Where Amazon SES falls short
The sandbox is the single biggest thing in this corpus
38 of 123 reviews, 31 percent, discuss the sandbox or production approval. That is the highest share any single theme reaches on any fiche on this site. The reason it matters is that the outcome is not predictable.
AWS commits to “an initial response to your request within 24 hours”, and one reviewer’s experience matches: “Initially you are sandboxed and have to apply to have this removed manually. It’s quick, however!” Others do not match at all. “I had to wait a month until an account from one of our customers was finally approved.” And the one that should give a founder pause: “I didn’t get the production access and I don’t send spam … Its seems they’re very picky who can use it.”
A fourth summarises the design tension neatly: “There are silent limits to SES that need to be lifted by reaching out to support. This is both a reasonable step to combat spam, and a frustrating discovery for those with legitimate intentions.” An initial response within 24 hours is not the same as approval within 24 hours, and nothing published tells you how long the second one takes or on what basis it is granted.
The free tier everyone quotes does not exist
Search for Amazon SES pricing and you will be told, repeatedly, that you get 62,000 emails a month free when sending from EC2. We read the pricing page twice looking for it. It is not there. Four reviews in this corpus cite it, which tells you how long it has lived in people’s heads.
What is published now: “New AWS customers will receive up to $200 in AWS Free Tier credits”, a free plan that is “available for 6 months after account creation”, and the constraint that “All Free Tier credits must be used within 12 months of your account creation date.” That is a credit and a clock, not an allowance. It is still generous, and it is a different thing.
A quarter of the corpus finds it hard, and the interface is why
Complexity is raised in 31 of 123 reviews and the console in 21. The picture that emerges is consistent: SES assumes you know AWS. You derive SMTP credentials from IAM. You wire Amazon SNS to receive bounce and complaint notifications, because they do not arrive any other way. There is no click tracking built in. There is no template designer in any meaningful sense.
The measurement agrees. Capterra rates SES 4.7 overall and 4.1 for ease of use, a 0.6 point gap that is the largest between a headline and a component we have found on this site. People rate the service highly and find using it hard, and both are true at once.
Support is a separate purchase, at the moment you most need it
Capterra’s customer service sub-score for SES is 4.0, and only 94 of 123 reviewers rated it at all, which is itself a signal. AWS Support is a paid tier, and the sandbox exit runs through it, so the one interaction every new account must have is with a function most accounts have not paid for. The variance in approval experiences above is the visible result.
No official MCP server, and the sample says so itself
We enumerated AWS’s own MCP catalogue: 62 servers, covering SNS, SQS, MQ, Lambda, Translate, IAM and much else. There is no SES entry.
What exists is a repository under the aws-samples organisation that exposes the SES v2 API actions through MCP, and its README states the position plainly: “This sample is not intended to be used in a production environment.” That is an honest label and we are repeating it rather than softening it. If you want an AI client to drive your sending, Drip ships a free official connector and GoHighLevel publishes an Anthropic-specific endpoint. AWS ships a sample.
Two AWS pages disagree about the bounce target
A small thing, but this site exists to catch small things. AWS’s enforcement FAQ says “you should maintain a bounce rate below 2%”. Its success metrics page says “Try to keep your hard bounce rate below 5%”. Both are official documentation. The enforcement thresholds, 5 percent for review and 10 percent for a pause, are consistent across both. We flag the discrepancy rather than resolving it, and we would aim at 2 percent.
Fifty recipients per message, and that is final
A hard limit of 50 recipients per message, counting To, CC and BCC together, marked not adjustable. SendGrid allows 1,000 per request. If your architecture batches recipients, this changes how you write the sending loop.
What real users actually say
Capterra holds 123 reviews for Amazon SES (product ID 179662) and we read all 123, across five pages. This is a complete population rather than a sample, so the percentages below describe everyone who has reviewed it there. Two of the five pages returned condensed rather than full verbatim text; we used those for theme counting and quoted only from the pages that returned complete text. Capterra records the sentiment split as 95 percent positive, 5 percent neutral, 0 percent negative.
What they praise
- Price. Raised in 15 rows and almost always as the reason to choose it.
- AWS integration. Lambda, SNS and CloudWatch named repeatedly.
- Reliability at scale. “robust platform … never faced downtime”.
- Fit for developers. The corpus is unusually technical and comfortable with that.
What they criticise
- Sandbox and approval, 38 rows (31%). The largest single theme on any fiche on this site.
- Complexity, 31 rows (25%). Assumes AWS knowledge you may not have.
- Console and interface, 21 rows (17%). There is barely one.
- Support, 15 rows. Paid, and on the critical path out of the sandbox.
- Missing features, 6 rows. No click tracking, minimal templating.
The mixed clusters
The highest rating on this site, from the hardest product on it. A Capterra average of 4.7 across 123 reviews is the best number in our whole dataset, and it comes from a service with no interface, a permission gate and a 4.1 ease score. The explanation is selection: the people who review SES are the people who got through the sandbox, and they are developers who wanted infrastructure rather than a product. The reviews of the people who were refused are mostly not here.
The gate is described as both correct and infuriating, often in the same review. Reviewers accept the anti-spam logic and resent the experience of it. That is the honest position and it is why we score the sandbox as a real cost rather than a formality.
Almost nobody complains about deliverability. Thirteen rows raise it and the tone is operational, about wiring SNS for bounces or the absence of click tracking, rather than about mail not arriving. For a service with no independent placement figure, a quiet corpus at this scale is the strongest evidence available.
Ratings breakdown
Six categories, each out of 10, judged against the same evidence rules on every platform we cover. The overall is the unweighted arithmetic mean, rounded to one decimal: 5.0 + 3.5 + 8.0 + 5.0 + 9.0 + 7.5 = 38.0, divided by 6, equals 6.3.
Ease of use, 5.0. A 4.1 Capterra ease score under a 4.7 headline, 31 rows describing complexity and 21 describing the console. Trivial if you live in AWS, genuinely difficult if you do not.
Automation, 3.5. There is essentially none, by design. Templates and contact lists exist in the v2 API; campaigns, journeys and behavioural triggers do not.
Deliverability, 8.0. No seedlist figure exists, and the surrounding evidence is the strongest in this family: published enforcement thresholds, automatic suppression, both standard and managed dedicated IPs, a trillion messages a year, and a corpus that raises placement thirteen times without complaining about it.
Support, 5.0. A 4.0 customer service sub-score, rated by only 94 of 123 reviewers, and a paid support product sitting on the critical path out of the sandbox.
Pricing value, 9.0. The highest score in this category on this site. $0.10 per thousand, a 4.6 value for money sub-score, and a corpus that raises price as praise. Held below 10 by the retired free tier and by attachment and dedicated IP charges that are easy to miss.
API and MCP, 7.5. A comprehensive v2 API across nineteen SMTP regions with SDKs for every major language. Held down by the absence of any official MCP server, by ten regions with no SMTP interface, and by a 50-recipient ceiling that SendGrid sets twenty times higher.
Who should use Amazon SES, and who should not
Amazon SES is the right call for
Look elsewhere if
Third-party validation
| Source | Score | Volume | Notes |
|---|---|---|---|
| Capterra | 4.7 / 5 | 123 reviews | The highest average on this site. Ease of use 4.1, value for money 4.6, customer service 4.0. Product ID 179662, listed as “Amazon SES”. |
| G2 | 4.3 / 5 | 203 reviews | Listed as “Amazon Simple Email Service (Amazon SES)”. Note the different product name between the two sites. |
| Trustpilot | N/A | – | No verified listing found. |
| Inbox placement | No figure | – | Never included in the seedlist panel, which has since been discontinued. |
The 0.4 point gap between Capterra’s 4.7 and G2’s 4.3 runs in the direction we now expect: the more technical audience rates it lower. We saw the same shape on SendGrid. The likely reason is that G2’s reviewers are comparing SES against purpose-built email platforms while Capterra’s are comparing it against paying more.
The internal gap is the more instructive one. A 4.7 headline sitting on a 4.1 ease score is the widest divergence we have measured on this site, wider than Kit’s or GoHighLevel’s. It is the arithmetic signature of a product people are glad exists and find hard to use.
Top 3 alternatives
| Alternative | Our score | Take it instead if |
|---|---|---|
| Postmark | 7.1 | Transactional mail your business depends on, and you want support that answers. Separate streams for transactional and broadcast, and none of the AWS overhead. Considerably more expensive per message and worth it below a few million. |
| SendGrid | 5.7 | You want to be sending in ten minutes with no approval gate, and a hundred emails a day free forever. Read our review’s suspension section before you commit anything critical to it. |
| Brevo | 7.7 | You need a relay and marketing email from one vendor with an actual interface. The only platform in our marketing set that publishes an SMTP relay on an entry plan. |
Continue reading
- Amazon SES SMTP settings, every regional endpoint and port
- Amazon SES API, v2 send, quotas and SDK coverage
- Amazon SES pricing, plans, attachments and dedicated IPs
- Amazon SES integrations
- SendGrid review
- Postmark review
Frequently asked questions
What is AWS SES?
Amazon Simple Email Service, launched on 25 January 2011, is AWS’s email sending service for transactional and bulk mail. It provides an SMTP interface and a REST API, no campaign tooling and almost no user interface, and it processes over a trillion messages a year for customers including Netflix, Duolingo and Amazon’s own retail business.
How much does Amazon SES cost?
The base rate without a plan is $0.10 per 1,000 emails. The Essentials plan has no monthly base fee and charges $0.16 per 1,000 up to 10 million a month, falling to $0.11 above 100 million. Pro adds a $105 monthly fee per account per region and Enterprise $500, both with slightly higher per-thousand rates in exchange for additional features. Attachments cost $0.12 per gigabyte, and dedicated IPs are $24.95 per month each on the standard option.
What is AWS SES pricing compared with SendGrid?
Not close. A million emails a month costs $100 at the SES base rate. SendGrid’s Pro plan starts at $89.95 a month for 100,000 emails, with per-email overages above that. SES is dramatically cheaper at volume; SendGrid is dramatically faster to start, because it has no sandbox and gives you 100 emails a day free forever.
Does Amazon SES have a free tier?
Not the one you have read about. The widely quoted 62,000 emails a month when sending from EC2 no longer appears on the pricing page, and we checked twice. What is offered now is up to $200 in AWS Free Tier credits, a free plan available for six months after account creation, and a requirement that credits be used within twelve months of that date.
What are the Amazon SES SMTP settings?
The hostname is email-smtp followed by your region and amazonaws.com, for example email-smtp.eu-west-1.amazonaws.com. Use port 25, 587 or 2587 for STARTTLS, or 465 or 2465 for a TLS wrapper connection. Your username is your SES SMTP username, which matches the AWS access key ID, and your password is a dedicated SMTP password that is not the same as your AWS secret access key. Note that ten AWS regions have no SMTP endpoint at all, including Milan, Zurich, Jakarta and Bahrain.
How do I get out of the SES sandbox?
In the SES console, open the Account dashboard, choose View Get set up page and then Request production access. You declare whether your mail is Marketing or Transactional, give a website URL, optionally add up to four contact addresses, pick English or Japanese, and tick an acknowledgement that you will only email people who requested it and that you handle bounces and complaints. AWS states that support provides an initial response within 24 hours. That is a first response, not an approval, and the reviews we read range from same-week to a month to refused.
Amazon SES vs SendGrid: which should I choose?
SES if you already run on AWS, send at volume, and can wait for approval. SendGrid if you want to be sending today, want an EU regional endpoint without a plan, or need to send to more than 50 recipients in one message. SES scores 6.3 with us and SendGrid 5.7, but the two lose their points in opposite places: SES on usability, SendGrid on support and account stability.
Does Amazon SES have an MCP server?
Not an official one. We enumerated AWS’s MCP catalogue and found 62 servers, none of them SES. There is a repository under the aws-samples organisation that exposes the SES v2 API actions through MCP, and its own README states that it is not intended for production use. Treat it as example code, not as a supported product.
Changelog
| Date | Change |
|---|---|
| 27 August 2026 | First publication. All 123 Capterra reviews read across 5 pages, the complete population. Every hostname pattern, port, quota, threshold and price verified twice against AWS documentation on this date, with the SMTP AUTH mechanism omitted because AWS does not name it. The retired 62,000-email free tier confirmed absent from the pricing page on two passes. AWS’s MCP catalogue enumerated in full. Search volumes measured for the United States. |
This review follows our email infrastructure testing methodology. We disclose affiliate relationships in our editorial independence policy.
