AWS SES cost: about ten cents per thousand emails

Quick answer

SES charges about $0.10 per 1,000 emails sent, plus about $0.12 per GB of attachments, a small charge for inbound email, and standard data transfer. It is among the cheapest ways to send transactional or bulk email at scale. The gotchas are attachment data, dedicated IPs, and deliverability, not the per-message price.

Amazon SES is priced to be boring: a fraction of a cent per email. For most applications the sending charge is trivial, and the interesting cost questions are around attachments, dedicated IPs, and the operational cost of deliverability rather than the per-message rate.

The per-message rate

Dimension	Rate (approximate)
Outbound email	~$0.10 / 1,000
Attachments	~$0.12 / GB
Inbound email	~$0.10 / 1,000
Data transfer	Standard rates

A million emails a month costs around $100 in sending charges, which is negligible for most businesses and far cheaper than most third-party email providers at volume.

Where the cost actually is

Attachment data can add up for services that send large files, so link to content in S3 rather than attaching it where possible. Dedicated IP addresses (for reputation control) carry a monthly fee per IP, worth it only at high volume with deliverability requirements. And the real cost of email at scale is deliverability work, warming IPs, handling bounces and complaints, not the SES bill.

SES vs third-party providers

SES is dramatically cheaper per message than most hosted email APIs, which is why teams move to it at volume. What you trade is the higher-level features, templates, analytics, and deliverability tooling, that those providers bundle. For high-volume transactional email where you can handle the operational side, SES is the low-cost choice.

FAQ

How much does AWS SES cost?

About $0.10 per 1,000 emails sent, plus about $0.12 per GB of attachments, a small charge for inbound email, and standard data transfer. A million emails a month costs around $100 in sending charges, which is negligible for most businesses.

Is SES cheaper than SendGrid or similar?

Per message, yes, usually by a wide margin at volume. What you trade is the higher-level features those providers bundle, such as templates, analytics, and deliverability tooling. For high-volume sending where you can handle the operational side, SES is the low-cost choice.

How do I reduce SES cost?

Link to large content in S3 rather than attaching it to reduce the attachment charge, avoid dedicated IPs unless volume and deliverability justify their monthly fee, and clean your recipient lists to avoid wasted sends to invalid or complaining addresses.

Do dedicated IPs cost extra on SES?

Yes, a monthly fee per dedicated IP address. They give you control over sending reputation, which matters at high volume with strict deliverability needs, but for most workloads the shared IP pool is fine and avoids the cost.

What is the real cost of email at scale?

Usually deliverability work, not the SES bill. Warming IPs, handling bounces and complaints, maintaining sender reputation, and list hygiene are the operational costs. The per-message SES charge is trivial by comparison.

Does C3X estimate SES cost?

SES cost is driven by email volume, a usage input. C3X prices the surrounding infrastructure, and you model sending volume to estimate the per-message charge, which is usually a small part of the bill.

What to do next

Estimate the infrastructure around your email pipeline before you build it. C3X reads your Terraform and prices your resources against a live catalog. Start with the quickstart.