Amazon SES for Beginners: Is It Worth the Setup?

Amazon SES comes up a lot when you look for cheap transactional email: the automatic emails your SaaS sends, like sign-up confirmations and password resets. Its prices are some of the lowest you'll find.

This guide to Amazon SES for beginners covers what SES is, why it costs so little, every setup step and who it suits. If you build with Claude Code but don't write code yourself, it also shows a service built for you.

What is Amazon SES?

Amazon SES (Simple Email Service) is the email sending service from Amazon Web Services (AWS). Your SaaS hands SES an email, and SES delivers it to the recipient's inbox provider.

SES is one of many services inside AWS, Amazon's cloud platform, and you manage it from the same AWS console as the rest. Your project can talk to SES in two ways:

• Through its API, a way for one piece of software to send instructions to another.
• Through SMTP, the standard method email servers use to pass messages along. Our guide to what SMTP is explains it in plain English.

It's a general-purpose building block, designed to be wired into products by developers.

Why is Amazon SES so cheap?

Amazon SES is cheap because you pay per email with no required monthly fee, and AWS runs it at enormous scale. Most small SaaS products spend a few dollars a month or less on sending.

Prices checked October 2026, for the first 10 million emails a month:

Every option also charges $0.12 per GB of attachment data you send.

One detail catches people out. Since July 21, 2026, new SES accounts start on the Essentials plan by default. If you want the $0.10 rate, you switch to à la carte pricing, which AWS lets you do at any time.

Here's what sending costs at typical volumes:

Other AWS services you connect to SES are billed separately. The bigger cost for beginners is time. For a wider view, see our transactional email pricing comparison and our roundup of the cheapest transactional email services.

What does setting up Amazon SES involve?

Setting up Amazon SES takes seven steps, including two waits on AWS and one on DNS. Here's the aws ses setup, as AWS's own docs describe it.

1. Create an AWS account. You enter an email address, a password, your contact details and a payment method, then verify your phone number and pick a support plan. Activation can take up to 24 hours.

2. Choose a Region. AWS runs SES separately in different parts of the world, called Regions. Your sandbox status, verified domains and sending credentials all belong to one Region.

3. Verify your domain. In the SES console, go to Configuration, then Identities, then Create identity, and choose Domain. SES gives you three DNS records to add where your domain's DNS is managed. DNS is the internet's address book; these records prove you own the domain. Changes can take up to 72 hours to take effect. Our guide on how to verify a domain for email walks through this step.

4. Ask to leave the sandbox. Every new SES account starts in a restricted "sandbox":

   Sandbox limit	What it means
   Who you can email	Only addresses and domains you've verified
   Daily limit	200 emails per 24 hours
   Speed	1 email per second

   Real customers can't get your emails until you request production access. In the SES console, open the Account dashboard, choose View Get set up page, then Request production access. You choose Transactional, enter your website and confirm that you only email people who asked to hear from you and can handle bounces and complaints. AWS replies within 24 hours, or longer if it needs more information.

5. Create sending credentials with the right permissions. AWS controls who can do what through IAM, its system for logins and permissions. You create either SMTP credentials (in the SES console under SMTP settings) or API access keys, with permission to send email. The SMTP password is shown only once, so you download or copy it before closing the window. Our guide to what an API key is explains why services use them.

6. Add the key and sending code to your project. The credentials go into your hosting settings as environment variables (secret settings kept outside your code), and Claude Code writes the code that sends each email. See where to put API keys for how that works.

7. Plan for bounces and complaints. Getting told about them means connecting SES to another AWS service, such as Amazon SNS, with its own settings and charges.

What is working with Amazon SES like day to day?

Working with Amazon SES day to day means working inside AWS. The console and docs are written for developers, and email settings are spread across SES, IAM and other AWS services.

A few things that come up once you're live:

• "Did my user get the email?" You check SES's sending statistics in the console, or the notifications you set up through other AWS services.
• Changing an email. Your email wording and design live in your project's code, so changes mean asking Claude Code to edit and redeploy it.
• Keeping credentials tidy. Sending keys belong to IAM users, and you manage, replace or delete them in the IAM console.

In September 2026, AWS released an Amazon SES skill for the AWS MCP Server. MCP (Model Context Protocol) is a standard way for AI tools like Claude Code to connect to outside services; our plain-English guide to MCP covers it. With it connected, Claude Code can guide you through tasks like verifying your domain, using plain-language requests.

It's a useful step, and it's still AWS. Connecting means signing in with an AWS login that has specific IAM permissions, and AWS's setup guide is written for developers. Once connected, Claude Code works with your AWS account as a whole, not with an email service designed around people who don't code.

Who is Amazon SES a good fit for?

Amazon SES is a good fit for people who write code, or want to edit code themselves, and are at home in AWS. It suits:

• Developers and technical founders who already know their way around AWS and IAM.
• Products already running on AWS, where SES sits next to everything else.
• Very high volumes, where saving fractions of a cent per email adds up to real money.

It's a weaker fit if you build with Claude Code, don't write code yourself, and would rather brief Claude Code in plain English than work through a cloud console. For a closer look at other options, see our guide to Amazon SES alternatives.

How is SimpleSends different for people who don't code?

SimpleSends is a transactional email service built for people who build with Claude Code but don't write code. Setup uses the same building blocks as any email service: an account, a verified domain, a secret key and sending code. What's different is who it's built for and what working with it is like afterward.

• Plain English throughout. The sign-up, the connect steps and the help are written without developer jargon.
• Everything after sign-up happens in the chat. You don't need a dashboard for day-to-day work. You brief Claude Code the way you'd brief a person.
• Claude Code does every part of the job. It designs, writes, builds and changes every transactional email your SaaS sends, from welcome emails to password resets and receipts.
• Problems get sorted in plain English. Claude Code can read send logs and delivery status through SimpleSends, so it can tell you whether an email went out and help work out why one didn't.

Here's how to connect SimpleSends:

1. Sign up on the SimpleSends website and follow the steps there to set up the email address you'll send from. To send from your own domain, this includes adding a few DNS records where your domain is registered.

2. In Claude Code, open Customize, then Connectors, choose Add, then Add custom connector. Use these details:

   Field	What to enter
   Name	SimpleSends
   MCP server URL	https://mcp.simplesends.com/mcp

3. When Claude prompts you to connect, log in to SimpleSends.

4. Back in the Claude Code chat, tell Claude Code you've connected it:

I've connected SimpleSends for all transactional email.

Claude Code takes it from there, including adding what your project needs to send email. Then brief it on what you want:

Set up all the transactional emails my SaaS needs. Start with a welcome email for new sign-ups and a password reset email, matching the look of my site. Send me a test of each one before they go live.

Expect Claude Code to propose a list of emails, show you drafts to approve and send test copies to your inbox. Once your project is live, real emails go out from your project through SimpleSends, not from the chat.

SimpleSends has a free Starter plan with up to 100 emails a day, a Launch plan at $14 a month for up to 2,000 emails a day and up to 10 sending domains, and a Growth plan at $59 a month with no daily sending limit.

To see how this compares with other approaches for people who don't code, read our guide to transactional email for non-developers.

So, is Amazon SES worth the setup for a beginner?

Amazon SES is worth the setup if you're comfortable with code and AWS, or you'll send enough email for its low prices to matter.

If you don't write code, the savings are usually a few dollars a month at early-stage volumes, while setup and upkeep sit in developer territory. A service built for working with Claude Code in plain English is likely the better match.