A SaaS app can send a password reset through Amazon SES, but SES does not create the reset flow or manage the customer list for a campaign. This Amazon SES email service guide explains the setup, costs, and operational choices so developers can decide what to run themselves and what to put in a managed layer.
Amazon Simple Email Service (Amazon SES) is Amazon Web Services’ cloud infrastructure for sending transactional and marketing email through an API or SMTP. It accepts email from an application and sends it to recipients. Teams using SES directly still need to provide or connect the tools that manage templates, contacts, campaigns, automations, and reporting.
What is the Amazon SES email service used for?
Amazon SES is an AWS service for sending email from applications. Common transactional messages include password resets, receipts, and shipping updates: each is triggered by a user action or account event. Marketing email, such as a product announcement or newsletter, is sent to an audience for promotion or engagement.
SES can send both types, but sending is not the same as operating a full email program. With SES alone, teams need to build or connect the components that select campaign audiences, schedule sends, manage templates, and coordinate automated journeys. A password reset might be composed by application code, while a promotional campaign needs audience and scheduling controls as well.
We combine those uses in Volanea: it sends through Amazon SES and brings transactional email, campaigns, and automations into one API. That is one managed approach, not a requirement for using AWS. A team with existing email tooling can keep that tooling and use SES as its sending infrastructure.
How Amazon SES email sending works
An application submits a message to SES using either its API or Simple Mail Transfer Protocol (SMTP). An API client sends structured message data, while an SMTP-enabled application or library submits the email through an SMTP connection. SES handles the sending step; the application or connected tool decides who receives the message, what it says, and when it goes out.
For example, a SaaS application can trigger a password-reset email after a user requests a reset. The request includes the recipient and a message containing the reset link. The same product might use an email platform to schedule a newsletter, with SES still providing the underlying sending infrastructure.
Amazon Simple Notification Service (Amazon SNS) has a different job: it distributes published messages from a topic to subscribers, which can include services such as Amazon SQS or Lambda. SNS email subscriptions are intended for internal system alerts, not marketing messages. Treat SNS as a notification and fan-out service, not as the interface for sending customer campaigns. AWS describes SNS as a topic-based publish-subscribe service.
How to set up Amazon SES to send email
The practical setup is a sequence of AWS configuration and DNS work. Console labels can change, so use the current SES screens for the exact navigation; the important pieces are the sending region, a verified identity, credentials, and a test send.
- Choose the AWS Region. Use the region where your application will send. Keep the choice explicit in application configuration so your credentials and SES endpoint refer to the same region.
- Verify a sending identity. Add a domain or email address in SES and publish the DNS records AWS provides. A verified domain is useful when your application sends from more than one address on that domain.
- Set up authentication records. For a custom MAIL FROM domain, AWS gives this example MX value:
10 feedback-smtp.<region>.amazonses.com. Its corresponding SPF TXT value is"v=spf1 include:amazonses.com ~all". Replace the region placeholder with the applicable region and publish the records with your DNS provider. AWS explains the custom MAIL FROM records. - Configure credentials and permissions. Give the application the SES permissions it needs, store secrets outside source code, and choose either API sending or SMTP. Then send a test to confirm the application can submit a message and inspect the resulting delivery events and logs.
- Check account sending status before launch. Confirm in SES whether the account can send to the intended recipients and what restrictions apply. Plan any required AWS access request before routing live product traffic; do not assume a successful test to one address proves production readiness.
For teams who prefer a managed path, Volanea lets users send to real recipients after verifying their domain, without requesting SES production access. Its guided setup helps configure SPF, DKIM, and DMARC and checks the domain setup automatically.
Amazon SES pricing: what affects the cost?
Amazon SES pricing depends on the chosen plan, volume, and optional services. On AWS’s pricing page, Essentials costs $0.16 per 1,000 emails for 0–10M emails / month, with no monthly account-per-region fee listed. Its higher volume rates are marginal: each rate applies only to emails within that tier, not to the entire volume. Attachments, dedicated IPs, and other optional features can add charges. See AWS’s Amazon SES pricing.
At 50,000 emails a month, the plan totals are:
| Option | Calculation at 50,000 emails a month | Monthly sending and plan total |
|---|---|---|
| Amazon SES Essentials | 50,000 ÷ 1,000 × $0.16 | $8/month |
| Amazon SES Pro | 50,000 ÷ 1,000 × $0.22 + $105 | $116/month |
| Amazon SES Enterprise | 50,000 ÷ 1,000 × $0.23 + $500 | $511/month |
| Volanea Growth | $20 monthly comparison-table price | $20/month; 50,000 emails/month |
The AWS Pro and Enterprise totals include their respective monthly account-per-region charges; other applicable charges are additional. Volanea’s pricing page also lists Free at $0 for 1,000 emails per month, Starter at $5 for 7,500, and Scale at $149 for 200,000. The plan cards show lower monthly equivalents with yearly billing: Starter $4 per month ($48 billed yearly), Growth $16 per month ($192 billed yearly), and Scale $119.20 per month ($1,430.40 billed yearly). Yearly billing costs 20% less and provides the same monthly credits.
These numbers compare different bundles, not identical services. At 50,000 emails, Essentials has the lower sending charge; Growth adds managed campaigns, visual workflows, unlimited contacts, and other platform features. Volanea sends over shared Amazon SES infrastructure and does not offer dedicated IPs. AWS lists dedicated IPs as an additional-cost option, so that capability is not part of this comparison.
Volanea’s plans have no overage billing: when monthly credits run out, sending pauses until the next month or an upgrade. One credit sends one email to one recipient, or two credits for an email with an attachment. Free requires no credit card, but emails carry a small “Sent with Volanea” footer; paid plans remove it. For cost planning, count the capabilities your team needs alongside the sending volume, rather than treating an SES sending rate as the total cost of an email system.
Deliverability, authentication, and monitoring essentials
Configure SPF, DKIM, and DMARC in DNS before sending from a production domain. SPF is an email validation standard designed to prevent spoofing. DKIM adds a digital signature to outbound messages, and DMARC uses SPF and DKIM alignment to help receiving systems handle unauthenticated email. For DMARC, AWS gives this example TXT value: "v=DMARC1;p=quarantine;rua=mailto:my_dmarc_report@example.com"; publish it at _dmarc.example.com with your domain substituted. AWS explains SES authentication and DMARC alignment.
A successful API response is not proof of inbox placement. Monitor email bounce and complaint rates, remove invalid addresses, and honor unsubscribes and suppressions. A bounce indicates an address could not receive the message; a complaint means a recipient reported it as unwanted. Sudden changes in either signal deserve investigation before increasing volume, because low sending cost does not guarantee inbox placement.
We include bounce and complaint handling and a reputation guard in Volanea; it slows sending before a bad list harms a domain. Our domain setup also guides SPF, DKIM, and DMARC configuration and checks the setup automatically. For more operational detail, see our email deliverability and sending guides.
Benefits and limitations of Amazon SES
SES gives developers control over the sending layer and can fit AWS-based applications that already manage their own infrastructure. Its pricing separates message volume from optional capabilities, and API and SMTP interfaces support different application setups. For a product that needs only application-triggered messages and already has templates, monitoring, and contact controls, direct SES can be a reasonable choice.
The trade-off is the surrounding work. Teams must either build or connect the systems for template management, campaign audiences, workflow automation, contact handling, and reporting. That means owning the integration and operational behavior as the application changes, not just the initial send call. A queue and retry strategy also matters for resilient application email; our guide to transactional email queue architecture covers that design problem.
The exact operational footprint varies by what the product sends and which AWS options it enables. For example, SES Mail Manager Open / mTLS Ingress Endpoints cost $50 / month / endpoint; charges apply even when an endpoint is closed, billing is pro-rata, and a complimentary authenticated ingress endpoint is also available. These ingress costs matter for teams processing inbound email, but are not part of a basic outbound-only estimate.
Amazon SES directly or through a managed email platform?
Use SES directly when your team values control over the sending layer and is willing to maintain the supporting tools. A product with a few transactional messages and an existing campaign system may have little reason to add another platform. If campaign setup, reusable templates, contact operations, and workflow automation are separate engineering projects, compare the time and maintenance as well as the AWS invoice.
A managed layer can keep SES as the delivery infrastructure while consolidating those email operations. Volanea includes a REST API and SMTP relay, campaigns, visual workflows, and unlimited contact storage. Its MCP server includes 23 tools on every plan, including Free, so AI coding agents can work with the email stack through that integration.
A practical 50,000-email comparison illustrates the trade-off: Amazon SES Essentials sends that volume for $8/month, while Volanea Growth is listed at $20/month for 50,000 emails and includes campaign and automation capabilities. The difference buys a broader workflow layer, not a dedicated IP; Volanea uses shared Amazon SES infrastructure. Choose direct SES if you want to assemble that layer yourself, or a managed service if the combined operating surface is worth the added plan cost.
For integration details, Volanea SMTP uses username volanea and the project’s secret API key as the password. We also provide a sk_test_ key for rendering and logging test sends; those messages are not delivered. For teams with compliance requirements, a BAA is available on request at hello@volanea.com. Volanea does not hold SOC 2 or ISO 27001 certification, so evaluate those requirements against your own procurement criteria.
FAQ
What happens when a Volanea plan reaches its monthly email limit?
Sending pauses when the plan’s credits run out; Volanea does not bill overages. Sending can resume at the next monthly reset or after an upgrade. Credits do not roll over, so teams with uneven sending patterns should size the plan for their typical monthly peak rather than relying on unused credits from a quieter month.
Can I send through Volanea with SMTP instead of its REST API?
Yes. Volanea supports an SMTP relay as well as a REST API. Use volanea as the SMTP username and the project’s secret API key as the password, and keep that key in your application’s secret store. The from field accepts either a bare email address or a formatted value such as Name <address>.
Do Volanea test keys deliver email to recipients?
No. A sk_test_ key renders and logs messages but does not deliver them. It is useful for checking message construction and application behavior without sending to real recipients. Switch to the project’s live secret API key when you are ready to send, and keep the test and live credentials clearly separated in your configuration.
Start free with 1,000 emails a month → https://app.volanea.com/signup