Amazon SES Pricing in 2026: Essentials vs A La Carte Costs

Amazon Simple Email Service no longer has one universal 2026 price. As of August 2026, new SES account-region combinations start on the Essentials plan at $0.16 per 1,000 emails through 10 million emails per month. A-la-carte outbound sending remains available at $0.10 per 1,000. Existing active customers can remain a la carte, and customers placed on Essentials can switch.

This guide explains which price applies, works through 10,000, 50,000, and 200,000 outbound emails under both structures, and separates optional services from the send rate. Source: Amazon SES pricing, verified as of August 2026. AWS announced the plan rollout on July 21, 2026 in its SES pricing plans launch note. Check the live pricing page before making a purchase decision.

The short answer: Essentials is $0.16 per 1,000, while a la carte is $0.10

For the first 10 million emails in a month:

• Essentials: $0.16 per 1,000 emails.
• A la carte: $0.10 per 1,000 outbound emails.

New SES accounts and account-region combinations with no metered SES activity since June 1, 2025 start on Essentials from July 21, 2026. AWS says customers can switch to a-la-carte pricing at any time. Account-region combinations with metered activity on or after June 1, 2025 remain a la carte unless they choose a plan.

Essentials is not simply a higher transport price. It includes SES deliverability features that are separately metered under a-la-carte pricing. Pro and Enterprise plans add more capabilities and fixed monthly charges, but this guide focuses on the two entry choices most relevant to the common $0.10 pricing question.

What each entry option includes

Essentials costs $0.16 per 1,000 emails through 10 million per month. The rate applies to outbound email sent or email processed through Mail Manager, with the outbound and inbound volume tiers calculated independently. SES deliverability features are included. Rates fall marginally above 10 million emails, so the examples in this guide all use the first tier.

A-la-carte outbound sending costs $0.10 per 1,000 emails. It has no mandatory plan fee. Add-ons such as Virtual Deliverability Manager are billed separately when used.

Attachment data sent costs $0.12 per GB. AWS labels this as data in the attachments you send, not a generic charge for the HTML or text body of every outbound message. The worked examples exclude attachment data because the amount depends on actual attachment size.

A Standard dedicated IP costs $24.95 per month for each IP. It is optional under either structure and is not included in the entry send rate.

A-la-carte Virtual Deliverability Manager costs $0.07 per 1,000 emails in the first 10 million. The SES deliverability capability is included in Essentials, so adding the same $0.07 line again to an Essentials example would double-count it.

Mail Manager endpoint pricing depends on the ingress type. Open and mTLS ingress endpoints cost $50 per month per endpoint. AWS provides a complimentary authenticated ingress endpoint that accepts mail from credentialed senders. Under a-la-carte pricing, Mail Manager email processing is $0.15 per 1,000 emails. Plan customers use the applicable plan rate for processed email.

Compute and integration are outside the SES line item. A team may use Lambda, SNS, S3, CloudWatch, and application storage depending on the architecture. Their cost depends on execution time, retention, event volume, and design, so this guide does not invent a flat estimate.

Dedicated IP and deliverability pricing

A Standard dedicated IP adds $24.95 per month under either entry option. At low volume, that fixed charge can exceed the send charge. It is optional, so a fair estimate must state whether it is included rather than presenting it as a required SES cost.

For a-la-carte customers, Virtual Deliverability Manager adds $0.07 per 1,000 emails through 10 million per month. Combined with $0.10 a-la-carte sending, the two usage lines total $0.17 per 1,000 before attachment data and any dedicated IP.

Essentials charges $0.16 per 1,000 and includes SES deliverability. Comparing $0.16 Essentials with $0.17 for a-la-carte sending plus VDM is closer to like-for-like than comparing Essentials with the $0.10 transport-only line.

Inbound processing and Mail Manager

Outbound sending and an application inbox are different layers. AWS Mail Manager ingress endpoints accept mail through Open, mTLS, or authenticated endpoints. Open and mTLS endpoints cost about $50 per month each; the authenticated endpoint is complimentary but only accepts mail from credentialed senders.

Mail Manager can process and route email, but your application still decides how recipients map to users or agents, how messages become threads, where searchable history lives, and how retention and access control work.

What SES does not bundle: a Bavimail product-layer view

The following points describe the product layer a team assembles around SES, not claims that AWS lacks infrastructure components.

Normalized application parsing is assembled from AWS services. SES receipt rules and Mail Manager route messages to actions such as S3 or Lambda. If your product needs a stable JSON webhook containing normalized text, HTML, headers, and attachment references, your team builds that contract on top of the AWS email receiving actions.

A persistent per-user or per-agent inbox is not bundled with SES transport. SES supplies identities, receipt rules, and routing actions. From Bavimail's product perspective, the inbox object, conversation history, threading, and tenant isolation remain application concerns built on services such as S3, Lambda, and a database.

Application storage is a separate architecture choice. The Amazon S3 receipt action can store raw messages, but storage, lifecycle, indexing, and retrieval are separate from the outbound send price.

The AWS console is not a unified customer inbox dashboard. AWS provides SES and related service consoles. A product that needs one application view across outbound state, inbound threads, identities, and end-user operations assembles that view from the underlying services.

For an AWS-native team, this composability can be the reason to choose SES. These boundaries are only disadvantages when the team wants the application-facing layer managed for it.

Worked example: 10,000 emails per month

At 10,000 outbound emails:

• Essentials send charge: $1.60.
• A-la-carte send charge: $1.00.

For a closer deliverability comparison:

• Essentials plus one Standard dedicated IP: $1.60 + $24.95 = $26.55. SES deliverability is already included.
• A la carte plus one Standard dedicated IP and VDM: $1.00 + $24.95 + $0.70 = $26.65.

Both totals exclude attachment data, inbound processing, and compute. Bavimail Pro is $5/mo, or $48/yr with a $4/mo equivalent, and includes up to 50,000 monthly emails plus its managed application surface. SES remains cheaper when transport alone is the requirement.

Worked example: 50,000 emails per month

At 50,000 outbound emails:

• Essentials send charge: $8.00.
• A-la-carte send charge: $5.00.

With the same optional deliverability stack:

• Essentials plus one Standard dedicated IP: $8.00 + $24.95 = $32.95.
• A la carte plus one Standard dedicated IP and VDM: $5.00 + $24.95 + $3.50 = $33.45.

Bavimail Pro covers 50,000 monthly emails for $5/mo, or $48/yr with a $4/mo equivalent. The $5 SES comparison is the a-la-carte transport-only price, not the default starting price for a new account-region combination and not a like-for-like comparison with Essentials deliverability included.

Worked example: 200,000 emails per month

At 200,000 outbound emails:

• Essentials send charge: $32.00.
• A-la-carte send charge: $20.00.

With the optional stack:

• Essentials plus one Standard dedicated IP: $32.00 + $24.95 = $56.95.
• A la carte plus one Standard dedicated IP and VDM: $20.00 + $24.95 + $14.00 = $58.95.

Bavimail Startup covers up to 300,000 monthly emails for $50/mo, or $492/yr with a $41/mo equivalent, and includes 30 GB retained storage. SES still has the lower transport-only line. The managed-platform comparison depends on whether the team wants to build the surrounding send-and-receive product layer.

When Amazon SES is the right choice

Amazon SES is a strong fit when:

• Your application already runs on AWS and the team is comfortable with IAM, SNS, S3, Lambda, and CloudWatch.
• You want to choose between an included deliverability bundle and a-la-carte transport.
• Raw per-email cost is the binding constraint, especially at high volume.
• You want full control over storage, routing, and application state.
• You have engineering capacity to build the inbox and product workflow you need.

At volumes above 10 million, SES plan rates decrease marginally, so high-volume buyers should calculate each tier from the current AWS table rather than extending either entry rate indefinitely.

When a managed platform is the better fit

A managed email platform is a better fit when time-to-production, a unified send-and-receive model, and inbox-level application primitives matter more than owning each AWS component.

Bavimail Pro is $5/mo, or $48/yr with a $4/mo equivalent, for 50,000 monthly emails and 5 GB retained storage. Bavimail Startup is $50/mo, or $492/yr with a $41/mo equivalent, for 300,000 monthly emails and 30 GB retained storage. Those prices cover a different product boundary: managed sending, inbound handling, identities, webhooks, and application-facing operations behind one API.

Read the Bavimail vs Amazon SES comparison for a feature-by-feature view, the transactional email API comparison for the seven-provider landscape, or Bavimail pricing for the current managed plans.

The bottom line

As of August 2026, the honest SES headline is a choice, not one universal rate. Essentials is $0.16 per 1,000 emails through 10 million per month and is the starting plan for new or inactive account-region combinations. A-la-carte outbound sending remains $0.10 per 1,000 and customers can switch to it.

At 10,000, 50,000, and 200,000 outbound emails, Essentials costs $1.60, $8, and $32. A-la-carte transport costs $1, $5, and $20. Quote the structure that actually applies, then add only the attachment data, ingress endpoint, dedicated IP, deliverability, inbound processing, compute, and storage lines the planned architecture uses.