
Amazon SES
Raw email-sending infrastructure from AWS.
Amazon Simple Email Service (SES) is AWS's service for sending and receiving email at scale, for both transactional and marketing mail. It provides the delivery infrastructure and leaves most of the surrounding tooling to you.
You verify identities (domains or single addresses) in an AWS region, then send through the SES API, usually via an AWS SDK or the CLI with IAM credentials, or through the SMTP interface with separate SMTP credentials. Delivery events (sends, deliveries, bounces, complaints, opens, clicks, rejections) are published through "configuration sets" to other AWS services: CloudWatch, SNS, EventBridge or Data Firehose. To receive mail, you point your MX records at the regional inbound endpoint, and receipt rules decide what happens to each recipient's mail.
Useful for a small team already on AWS: an account-level suppression list; Virtual Deliverability Manager, which gives deliverability insights and recommendations; IP filters for inbound mail; and availability in many AWS regions, each spread across several availability zones. SES is on AWS's list of HIPAA-eligible services.
New accounts start in a sandbox in each region: only verified recipients, at most 200 messages per 24 hours and 1 per second, until AWS approves a production-access request. It isn't a mailbox: the inbound endpoints don't serve IMAP, so you can't read received mail in an email client.
Where it fits
Who uses it
4 makers' products, each linked to the source that shows it, and 32 open-source projects that declare it in their code.
Open source: a project that declares Amazon SES as a dependency in its public code — verifiable, but not necessarily a live product.
Loved and watch-outs
Themes that recur in makers' words and Hacker News comments, each linked to what it summarises.
Who switches
Public pull requests on GitHub since Oct 2024 whose title says "X to Y" — real code changes moving a project from one tool to another, by developers in general. Open a row to see the pull requests.
Resend → Amazon SES15 PRs
- refactor(email): migrate email sending from Resend to Amazon SESethnjs/nexus · 2026-09-26
- [TASK-325] Move all email from Resend to Amazon SESjpj-youtube-ai/nbcc · 2026-08-31
- feat(mail): migrate email delivery from Resend to AWS SESZobeir-Rigi/Career-Mentors-Matching · 2026-08-13
- feat: swap contact form from Resend to AWS SESAI-Institute-Food-Systems/foodatlas · 2026-07-17
- EXP-108: migrate transactional email from Resend to Amazon SESNiach/exponential · 2026-07-15
- 3047 - Migrate report email delivery from Resend to Amazon SESValuatumOy/AI-company-valuation-raportti · 2026-07-14
- Switch outbound email from Resend to Amazon SESNooh-wq/solvr · 2026-07-04
- feat(email): migrate from Resend to Amazon SESFujiwaraChoki/supoclip · 2026-06-30
- Alerts: switch email sending from Resend to Amazon SESnrdptel/Hobby-Rocket-Motor-Finder · 2026-06-06
- feat(email): migrate from Resend to AWS SESS-3-Research/Demos · 2026-05-15
SendGrid → Amazon SES12 PRs
- Sendgrid to ses cost reductioncm-igarashi-ryosuke/zenn-connect · 2026-09-11
- Migrate email service from SendGrid to Amazon SESindentlabs/notebook · 2026-08-06
- Migrate email from SendGrid to Amazon SES (SMTP)wrenchtokeys/rswr_systems · 2026-07-10
- feat(email): migrate cookiecutter default from SendGrid to AWS SEShmesfin/my-django-cookiecutter · 2026-05-19
- Switch email from SendGrid to Amazon SES with redesigned templateskresnajenie/merfisheyes · 2026-03-29
- Migrate email service from SendGrid to AWS SESk2bg-technology/k2bg-branding · 2026-02-03
- Migrate email service from SendGrid to AWS SEShackforla/food-oasis · 2026-01-13
- Migrate email delivery from SendGrid to AWS SESGratheon/user-cycle · 2025-09-17
- update: migrate email sending from SendGrid to Amazon SESnerubia/kh360-nodejs · 2025-08-20
- update: migrate email sending from SendGrid to Amazon SESnerubia/kh360-nodejs · 2025-08-05
Amazon SES → Resend16 PRs
- feat: switch email delivery from SES to Resendfilippofortino/filemax · 2026-09-29
- Switch transactional email from SES to Resendmark-mcdermott/frunk · 2026-09-19
- feat: migrate login-code email from SES to Resendafsting/developer-experience-concepts · 2026-09-07
- Switch demo form email delivery from SES to Resenddatalign-technology/procela-website · 2026-07-24
- feat: migrate notification service from SES to Resend with audit trailFIAP-13SOAT/media-processor · 2026-07-14
- feat(email): migrate transactional email from AWS SES to ResendZen-TM/logjam · 2026-06-18
- Switch transactional email from SES to Resend; fix digest linksbballhaus/civitas · 2026-05-26
- Migrate email sending from AWS SES to Resend APIjbaranski/majorleaguesoccer-today · 2026-05-23
- Update Novantt template: migrate from Amazon SES to ResendDomain-Connect/Templates · 2026-05-21
- Claude/migrate ses to resend r8sj yjbaranski/majorleaguesoccer-today · 2026-05-20
Amazon SES → SendGrid4 PRs
- Newsletter Studio: a listmonk-style campaign engine, with an Amazon SES transport to replace SendGridShawnDaPrawn/NavigateWealth · 2026-08-29
- Migrate email service from AWS SES to SendGridmaronnjapan/maronn-household · 2026-01-28
- changed from ses to sendgridTushar-cloud-org/serverless · 2025-11-08
- update: use ses to replace sendGridice-solution/eventCheckinSystem · 2025-07-06
Alternatives to Amazon SES
All alternatives by situation →Questions makers ask about Amazon SES
Can I send to any address as soon as I sign up?
No. New accounts are in a sandbox where you can only send to verified addresses or the mailbox simulator, up to 200 messages a day and 1 per second. You leave it by requesting production access in the console, describing your use case and website. source ↗
Does production access apply to every AWS region?
No. Sandbox status and sending limits are set per region, so an account approved in one region can still be in the sandbox in another. source ↗
Do I still have to verify sender addresses after leaving the sandbox?
Yes. You can then mail any recipient, but every From, Source, Sender and Return-Path address must still be a verified identity. source ↗
How do I find out about bounces and complaints?
Set up a configuration set that publishes events such as bounces, complaints, deliveries and opens to SNS, EventBridge, CloudWatch or Firehose, and name it when you send. source ↗
Can I use it from an existing SMTP library or app?
Yes. SES has an SMTP interface that works with SMTP-capable languages and software; you generate SMTP credentials for it. source ↗
Can I read received email in Outlook or another mail client?
No. The inbound SMTP endpoints aren't IMAP servers. SES hands received mail to your receipt-rule actions; AWS points to Amazon WorkMail if you need mailboxes. source ↗
Can I use SES for health data under HIPAA?
SES appears on AWS's list of HIPAA-eligible services, which are covered once you have a Business Associate Addendum with AWS. source ↗
Is Amazon SES free?
No permanent free tier; paid use starts at $0.10 per 1k emails. source ↗
Is Amazon SES open source or self-hostable?
Not open source, and hosted only.
Can AI coding agents work with Amazon SES?
No llms.txt, official MCP server or CLI found yet.
Who uses Amazon SES?
4 makers' products we track, each with a source, and 32 open-source projects declare it in their code. source ↗