Amazon SES Pricing Plans (Jul 2026): Essentials vs Pro vs Enterprise — When to Switch

On July 21, 2026, AWS introduced Amazon SES pricing plans — three hierarchical options (Essentials, Pro, Enterprise) that bundle deliverability capabilities instead of forcing every team to evaluate managed IPs, Virtual Deliverability Manager, validation, Global Endpoints, and tenants as separate line items. Rates and inclusions are published on the Amazon SES pricing page.

This is a billing-model change, not a new send API. If you only buy outbound email at $0.10 per 1,000, a plan can raise your unit cost. If you already stack managed dedicated IPs + Global VDM + validation, Pro can cut hundreds to thousands of dollars per month — AWS’s own 2M-email Pro example lands at ~$552.68/mo; our Pro-like a-la-carte reconstruction at the same volume is ~$1,792.68/mo (~$1,240/mo delta before Mail Manager inbound).

This guide is for FinOps leads, email platform owners, and CTOs deciding which plan (if any) to select — and when to stay a-la-carte. For hands-on SES deliverability work, see our Amazon SES consulting and SES migration services.

Amazon SES pricing plans (as of July 21, 2026) replace à-la-carte shopping for many deliverability features with Essentials / Pro / Enterprise tiers. Pro adds $105/account/region/month; Enterprise adds $500. New and idle-since-June-1-2025 accounts default to Essentials. À-la-carte remains available.

What Changed on July 21, 2026

Before pricing plans, SES sold outbound send cheaply and metered most deliverability capabilities separately — Virtual Deliverability Manager, managed dedicated IPs, email validation, Global Endpoints, tenants, and Mail Manager options each had their own math. Teams that wanted a production-grade stack had to assemble the bill piece by piece.

With pricing plans:

• Essentials includes outbound send + Virtual Deliverability Manager (SES deliverability). No monthly fixed fee. Higher per-1k send rate than a-la-carte.
• Pro builds on Essentials and adds managed dedicated IPs (1 domain, 1 managed DIP, 5 seedlist tests), email validation allowances, Global VDM, and Mail Manager email add-ons (Trend Micro). Fixed fee $105/account/region/month.
• Enterprise builds on Pro and adds Global Endpoints, tenants (1,000 included), open ingress (1 included), broader Mail Manager add-ons, and — for qualifying long-term high-volume customers — an annual deliverability assessment. Fixed fee $500/account/region/month.

Defaulting rule: new SES accounts and accounts with no metered SES activity since June 1, 2025 start on Essentials. You can upgrade or switch to a-la-carte in the SES console pricing plan section at any time.

Region caveat: plans are unavailable in Middle East (UAE) and Middle East (Bahrain). Everywhere else SES exists, plans are offered.

Plan Rates and Inclusions

Architecture detail for the Enterprise-only (or Enterprise-included) features lives in our SES tenant management guide and Global Endpoints / MREP guide.

First-Party Break-Even: Plan vs A-la-carte

We rebuilt AWS list-price math into a reproducible worksheet at fixed volumes (250k / 2M / 10M / 50M / 200M). Assumptions: 32 KB average message, outbound only (no Mail Manager inbound), one account/region, Pro-like stack = send + VDM SES + Global VDM + managed DIP + auto validation, Enterprise-like = Pro-like + Global Endpoints + open ingress + 100 tenants.

Reading the table:

• Send-only always wins on pure cost versus any plan at these volumes — because plan unit rates start above $0.10/1k.
• Pro undercuts Pro-like a-la-carte at every row once Global VDM’s $1,250/mo flat fee is in play (at 2M: ~$1,240/mo savings).
• Enterprise undercuts Enterprise-like a-la-carte when you need MREP + tenants + open ingress bundled (at 50M: ~$3,665/mo delta in this model).

Reproduce this — Open the break-even CSV and README. Plug your monthly volume and only the add-ons you actually enable. Re-check aws.amazon.com/ses/pricing before locking a budget — list prices move.

Opinionated Recommendation

We recommend a-la-carte for send-only and light VDM workloads; Pro when you would buy managed DIPs + Global VDM + validation anyway; Enterprise when MREP and tenants are non-negotiable and volume absorbs the $500 fixed fee. The trade-off: plans simplify procurement and discount bundled capability, but they punish bare-send economics and multiply fixed fees across every region you enable.

What broke — Day-one plan upgrade for a mid-volume transactional sender that used shared IPs and no Global VDM. They moved from a-la-carte $0.10/1k to Essentials $0.16/1k (or worse, Pro with the $105 fixed fee) expecting “better deliverability pricing.” Unit cost rose immediately; inbox placement did not, because authentication and list hygiene were unchanged. Detected on the first full billing cycle via Cost Explorer SES line items. Fix: switch back to a-la-carte until managed DIPs or Global VDM are on the roadmap, then re-run break-even.

That failure mode is the mirror image of the Pro win: plans discount capability stacks; they do not discount raw send.

How Plans Interact With Migrations and High-Volume Ecommerce

If you are leaving SendGrid, Mailgun, or similar ESP platforms, plan choice is a second-order decision after DNS, IP warming, and API cutover — see SendGrid → SES, Mailgun → SES, and the SendGrid migration guide. Land on a-la-carte or Essentials during warm-up; re-evaluate Pro once dedicated IP and Global VDM requirements are clear.

Ecommerce and marketing-automation senders already deep on SES (configuration sets, dedicated IPs, BIMI) should map current add-ons to plan inclusions before renewing anything. Our SES ecommerce email marketing and BIMI on SES posts cover the operational side; this post only settles the commercial model. For a published high-volume scale reference (not this post’s engagement silhouette), see the SES case study at 200M+ emails/month.

What to Do This Week

1. Open the SES console → pricing plan section and note whether you are on Essentials (default) or a-la-carte.
2. Inventory add-ons you pay for today: VDM (SES / Global), managed vs standard DIPs, validation, Global Endpoints, tenants, open ingress.
3. Run the worksheet at last month’s outbound volume with only those add-ons enabled.
4. Decide: stay a-la-carte, take Pro, or take Enterprise — and list every region where a fixed fee would apply.
5. If Pro/Enterprise wins, schedule the console switch and update FinOps forecasts; if not, document why so the next pricing page change does not trigger a reactive upgrade.
6. Book a deliverability + pricing review if the stack spans multiple brands or ISV tenants — contact us or start from Amazon SES consulting.

What This Post Doesn’t Cover

• Mail Manager architecture, archiving, and inbound routing design.
• IP warming schedules and reputation remediation playbooks.
• Full provider migration cutovers (covered in the migration guide and compare pages linked above).
• Exact Enterprise annual deliverability assessment eligibility (AWS gates that on trailing volume and subscription tenure — ask your account team).
• Live Cost Explorer screenshots from a production account (this post uses AWS published examples + the public worksheet only).

FAQ

What are Amazon SES pricing plans?

As of July 21, 2026, Amazon SES offers three hierarchical plans — Essentials, Pro, and Enterprise — that bundle deliverability capabilities at a discount versus buying the same features a-la-carte. Each plan has its own tiered per-1,000-email send rate; Pro adds a $105/account/region/month fixed fee and Enterprise adds $500.

Should I switch from a-la-carte to an SES pricing plan?

Switch when the features you already buy (or need next) are included in a plan and the plan total is lower than your current a-la-carte stack. Stay on a-la-carte if you only need outbound send — plan unit rates start at $0.16/1k (Essentials) versus $0.10/1k a-la-carte, so bare send gets more expensive on a plan.

When should I NOT choose the SES Pro plan?

Skip Pro if you do not need managed dedicated IPs, Global Virtual Deliverability Manager, or email validation. Paying $105/region plus a higher per-1k rate without using those inclusions is pure waste. Also skip Pro in regions where you send almost nothing — the fixed fee is per account per region.

When should I NOT choose the SES Enterprise plan?

Skip Enterprise for single-region transactional senders that do not need Global Endpoints (MREP), tenants, or Mail Manager open ingress. The $500/region fixed fee and $0.23/1k base tier only pay off when those Enterprise inclusions replace expensive a-la-carte lines you would buy anyway.

Do new SES accounts start on Essentials?

Yes. New SES accounts and accounts with no metered SES activity since June 1, 2025 start on Essentials beginning July 21, 2026. You can upgrade or switch back to a-la-carte at any time in the SES console pricing plan section.

Are SES pricing plans available in every region?

Plans are available in all AWS Regions where Amazon SES is available except the Middle East (UAE) and Middle East (Bahrain) Regions. Confirm current availability on the AWS SES pricing page before budgeting multi-region rollouts.

What could go wrong if I pick the wrong SES plan?

The common failure is upgrading to Pro or Enterprise for “better deliverability” while still only needing outbound send. Unit rates rise ($0.10 → $0.16–$0.23 per 1k) and fixed fees stack per region, so the bill can jump without any inbox-placement gain. Inventory add-ons first; then run the break-even worksheet at your volume.

Does Enterprise include SES tenant management and Global Endpoints?

Yes. Enterprise includes tenants (1,000 included per account per region) and Global Endpoints; both remain add-ons on Essentials and Pro. See our tenant management guide and Global Endpoints (MREP) guide for architecture detail beyond the pricing decision.