Amazon Simple Email Service (SES)

Amazon Simple Email Service (Amazon SES) is the AWS service for sending transactional and marketing email from applications through an API or SMTP. This Amazon SES overview focuses on what most new users need to understand first: how the sandbox works, how to request production access, and how responsible sending keeps your account in good standing.

What Amazon SES does #

SES is sending infrastructure, not a newsletter tool with templates and subscriber management built in. Your application or email platform hands messages to SES, and SES handles delivery, authentication signing and feedback. Its main components are:

• Sending interfaces: the SES API (via AWS SDKs and CLI) and an SMTP endpoint that works with most frameworks and mail libraries.
• Verified identities: the domains and email addresses you are allowed to send from. Domain verification uses DNS records.
• Easy DKIM and custom MAIL FROM: signing and envelope settings that support SPF, DKIM and DMARC alignment.
• Configuration sets and event publishing: route delivery, bounce, complaint, open and click events to services such as Amazon SNS, CloudWatch, EventBridge or Data Firehose.
• Suppression list: an account-level list that stops sending to addresses that bounced or complained.
• Dedicated IPs and Virtual Deliverability Manager: optional features for high-volume senders who want their own IP reputation and deliverability insights.

SES can also receive email and pass it to S3, Lambda or SNS, which is useful for processing replies or inbound messages.

The SES sandbox #

Every new SES account starts in the sandbox in each AWS region. The sandbox exists to protect recipients and the shared reputation of SES sending infrastructure. While in the sandbox:

• You can only send to verified email addresses and domains, or to the SES mailbox simulator.
• You have a small daily sending quota and a low maximum send rate. At the time of writing these are 200 messages per 24 hours and one message per second; check the SES documentation for current values.
• The restrictions apply per region, so moving to a new region means requesting production access there too.

The sandbox is the right place to build and test your integration: verify your domain, set up DKIM, send test messages and confirm your bounce and complaint handling works. Our guide to the Amazon SES sandbox, sending quotas and responsible email covers each step.

Requesting production access #

To send to any recipient, request production access from the SES console (the account dashboard includes a request option). AWS reviews each request, and a clear, honest description matters. Be ready to explain:

1. The type of email you send (transactional, marketing or both) and your website URL.
2. How recipients sign up or opt in, and how they unsubscribe.
3. How you process bounces and complaints, for example removing addresses automatically.
4. Expected sending volume.

AWS may approve the request, ask for more information or decline it. If more information is needed, reply through the same support case. After approval, your account receives a sending quota and rate; as you build a good track record, you can request increases through the official quota process.

Responsible sending #

SES monitors every account’s bounce rate and complaint rate, visible in the reputation metrics in the console. If they rise too high, AWS may place the account under review or pause sending until the cause is fixed. Good practice keeps you well clear of that:

• Only email people who asked to hear from you. Never use purchased or scraped lists.
• Authenticate your domain with SPF, DKIM and a DMARC policy. Major mailbox providers now expect this from bulk senders. See our guide to SPF, DKIM and DMARC for application senders.
• Include a clear unsubscribe option in marketing email, including one-click unsubscribe headers where required.
• Handle bounce and complaint notifications automatically and suppress those addresses.
• Keep transactional and marketing mail in separate configuration sets, or separate subdomains, so one does not harm the other.

How pricing works #

SES is pay-as-you-go: you are charged per batch of messages sent plus data for attachments, with separate charges for optional features such as dedicated IPs, Virtual Deliverability Manager and inbound email. There is no minimum commitment. Free tier terms for SES have changed over time, so confirm details on the official pricing page.

Where it fits and things to consider #

SES fits applications that send password resets, receipts, notifications and permission-based newsletters at any scale, especially if you already run on AWS. It is less suitable if you want a drag-and-drop campaign editor; many teams pair SES with a separate email marketing tool or build their own templates. Deliverability ultimately depends on your list quality and content, not only on the sending service.

Getting started the official way #

1. Create or use an existing account on the official Amazon SES page, and secure the root user with MFA.
2. Choose a region, verify your sending domain and publish the DKIM records.
3. Test in the sandbox, set up bounce and complaint handling, then request production access.
4. Follow the Amazon SES documentation for API, SMTP and configuration set details.

NewCloudStore is independent and not affiliated with Amazon Web Services; trademarks belong to their owners.