SES

Amazon SES (Simple Email Service)

AWS's transactional and bulk email-sending service — part of Amazon Web Services (Nasdaq: AMZN), launched in 2011 as Amazon Simple Email Service. Priced at $0.10 per 1,000 outbound emails ($0.0001/email) in 2026 — the cheapest production-grade email rail on the market by roughly an order of magnitude vs SendGrid / Postmark / Mailgun / Mailjet. AWS-grade deliverability infrastructure, full SPF / DKIM / DMARC, dedicated IP pools, Configuration Sets, event publishing (SNS / Kinesis / CloudWatch), Virtual Deliverability Manager and Mail Manager. Free-tier mechanics changed on 15 July 2025 — accounts created before that date get 3,000 free message charges/month for 12 months; accounts created after get $200 AWS Free Tier credits applicable to SES.

Transactional email / Email API / AWS 4.5 / 5 $0.10 per 1,000 outbound emails (~₹8.40 at ~₹84/USD); free tier varies by AWS account creation date Updated May 2026 🌍 US-headquartered (AWS / Amazon); USD billing via AWS Inc. with 18% IGST reverse-charge for Indian B2B
✅ Recommended for Indian product / fintech / e-commerce / consumer-app teams sending genuinely transactional high-volume email — cheapest production-grade email rail by an order of magnitude — but the wrong choice for marketing automation, journeys, drip campaigns or engagement orchestration (use a purpose-built engagement platform on top of or alongside SES)

Quick Verdict

Amazon SES is the canonical transactional email-sending rail for any team that has accepted the trade-off Amazon's AWS philosophy implies: genuinely cheap delivery at AWS-grade scale, in exchange for managing your own deliverability, templates, journey logic, suppression lists, and analytics. The service was launched in January 2011 as Amazon Simple Email Service and is part of Amazon Web Services (Nasdaq: AMZN, the public-cloud business of Amazon.com Inc.), with the typical AWS commercial profile: pay-as-you-go USD pricing, no minimum, no platform fee, no contract, and integration that lives or dies on AWS SDK / IAM / VPC competence at your end. The 2026 unit economics are blunt: $0.10 per 1,000 outbound emails — equivalent to $0.0001 per email, or roughly ₹8.40 per 1,000 emails / ₹0.0084 per email at ~₹84/USD. For comparison, SendGrid (now Twilio SendGrid) starts at $19.95/month for 50K emails (~$0.40/1,000, ~4× SES), Postmark starts at $15/month for 10K emails (~$1.50/1,000, ~15× SES), and Mailgun starts at $35/month for 50K emails (~$0.70/1,000, ~7× SES). Critical 2025 change worth flagging: the SES free tier mechanic changed on 15 July 2025. AWS accounts created before 15 July 2025 get the historical free tier — 3,000 free message charges per month for 12 months after starting SES (any combination of sends or receives counts as a "message charge"). AWS accounts created on or after 15 July 2025 get the new AWS-wide Free Tier model — $200 in AWS Free Tier credits applicable to SES and other AWS services. One subtle gotcha: if you enable Virtual Deliverability Manager, each email counts as TWO message charges, which doubles your effective cost and free-tier burn rate. For Indian buyers in 2026 the right framing is: SES is the default-correct call for any production team sending genuinely transactional email at volume (OTP emails, password resets, receipt emails, account-confirmation emails, order-status updates, system alerts) — the cost gap vs SendGrid / Postmark is large enough to justify the additional operational burden of managing deliverability and templates yourself. It is the wrong call for marketing automation (drip campaigns, lifecycle journeys, segmentation, A/B testing) — use a purpose-built engagement platform like WebEngage / MoEngage / Clevertap / Mailchimp / Loops / Customer.io that may itself send through SES under the hood. It is also the wrong call when your team genuinely cannot manage AWS competence (IAM, SDK, region selection, deliverability monitoring) — in which case Postmark's "boring works perfectly" simplicity is worth the price premium.

Unit economics (cheapest by far)
4.9
AWS-grade deliverability infrastructure
4.6
Transactional email fit (OTPs / receipts / alerts)
4.8
Marketing automation / journey orchestration
1.8
Out-of-box deliverability without ops
3.0

What is Amazon SES?

Amazon SES is a transactional and bulk email-sending service exposed as a simple REST API and SMTP endpoint. The mental model: where a CRM (Salesforce, HubSpot) handles pre-sale relationships, a CDP (Segment, RudderStack) handles customer-data plumbing, and an engagement platform (WebEngage, MoEngage, Clevertap) handles journey orchestration, SES is the actual rail that gets an email from your server to a customer's inbox — the email-delivery counterpart of what FCM is for push notifications and what Twilio / MSG91 are for SMS.

The service was launched in January 2011 as Amazon Simple Email Service (SES) as one of the earlier AWS managed services, built on top of Amazon's own internal email infrastructure that powers Amazon.com order confirmations, marketing emails and Prime / AWS notifications. The strategic logic was the AWS-standard one: take an internal service that Amazon had spent years building to massive scale, expose it as a managed AWS product, and let third-party developers buy it at a fraction of the cost of building or buying alternative providers. SES sits inside Amazon Web Services (Nasdaq: AMZN — the public-cloud arm of Amazon.com Inc., which posted ~$110 billion in 2024 annualised AWS revenue), and inherits all the standard AWS surface: IAM-based authentication, multi-region deployment (us-east-1, us-west-2, eu-west-1, ap-south-1 Mumbai, ap-southeast-1 Singapore, etc.), VPC connectivity, CloudWatch monitoring, CloudTrail audit logs, and integration with the broader AWS notification stack (SNS, Kinesis, Lambda).

The 2025–2026 product surface has expanded materially beyond simple SMTP / API send:

  • Email sending (the original product) — REST API and SMTP endpoint for outbound email; default sandbox limit 200 emails/day until you request production access; production accounts scale to millions per day
  • Email receiving — SES can also receive inbound email and trigger Lambda / S3 / SNS workflows; useful for reply-handling automation
  • Configuration Sets + Event Publishing — granular event delivery (deliveries, bounces, complaints, opens, clicks, rejects) to SNS / Kinesis / CloudWatch for analytics pipelines
  • Dedicated IP Pools — for high-volume senders who want isolated reputation; standard rate $24.95/month per dedicated IP plus the standard per-email charges
  • Virtual Deliverability Manager (VDM) — 2023–2024 launch — managed deliverability monitoring, sender-reputation insights, AI-led recommendations. Critical gotcha: each email counts as TWO message charges when VDM is enabled
  • Mail Manager (2024) — managed email routing, advanced rules, archive / e-discovery, anti-spam / anti-malware filtering for inbound email
  • SES Mailbox Simulator — sandboxed testing for bounce / complaint / OOO scenarios without affecting reputation

The 2025 free-tier mechanic change is worth understanding precisely because it changes the recommendation depending on when your AWS account was created:

  • AWS accounts created BEFORE 15 July 2025 — historical SES free tier: up to 3,000 message charges per month for 12 months after starting SES. Sending counts as one message charge; receiving counts as one. Suitable for prototyping and small production workloads.
  • AWS accounts created ON OR AFTER 15 July 2025 — new AWS-wide Free Tier model: $200 in AWS Free Tier credits applicable to SES and other AWS services. The $200 covers approximately 2,000,000 SES sends if used entirely on SES — meaningfully more generous than the legacy free tier if you want to use it that way, but the credits cap covers the whole AWS account.

What Amazon SES gives you (the product surface)

📧 Transactional sending — API + SMTP

Send via REST API (SendEmail, SendRawEmail, SendBulkTemplatedEmail) or SMTP endpoint. Production sandboxes scale to millions/day after limit-increase request. The bread-and-butter use case: OTPs, password resets, receipts, order confirmations, system alerts.

💸 $0.10 per 1,000 outbound emails

The blunt unit-economic case for SES. ₹8.40 per 1,000 emails at ~₹84/USD. Compare: SendGrid ~$0.40 / 1,000, Postmark ~$1.50 / 1,000, Mailgun ~$0.70 / 1,000. The cost gap is large enough that any team sending 10M+ emails/month saves ₹2-12 lakh/year vs purpose-built email APIs.

🌐 Dedicated IP pools

For senders who want isolated sender reputation, dedicated IPs at $24.95/month each. Useful when you're sending genuinely high volume (1M+ emails/month) and your reputation is the differentiator from spam.

🎯 Virtual Deliverability Manager (VDM)

2023–2024 addition — managed deliverability monitoring, sender-reputation insights, AI-led recommendations on warm-up, content, list hygiene. Critical billing gotcha: enabling VDM means each email counts as TWO message charges, doubling cost.

📥 Email receiving + Mail Manager (2024)

Inbound email handling with Lambda / S3 / SNS triggers; Mail Manager (2024) adds managed routing, archive / e-discovery, anti-spam / anti-malware filtering. Useful for reply-handling automation and compliance archival.

📊 Event publishing to SNS / Kinesis / CloudWatch

Granular event streams for delivery, bounce, complaint, open, click, reject — published to SNS / Kinesis / CloudWatch. The data plumbing layer most production teams build analytics dashboards on top of (vs SES's bare-bones built-in dashboard).

Pricing — how Amazon SES actually costs Indian buyers

Amazon SES is pay-as-you-go USD pricing via AWS Inc.; no minimum, no contract, no platform fee. The 2026 pricing structure:

  • Outbound email sends$0.10 per 1,000 outbound emails (= $0.0001 / email; ~₹8.40 / 1,000 emails at ~₹84/USD)
  • Inbound email received$0.10 per 1,000 incoming chunks (an email is metered as 256-KB chunks of data)
  • Outgoing data charges — separate data-transfer charges on attachments beyond the standard email size (typically negligible for ordinary transactional sends)
  • Dedicated IPs$24.95/month per dedicated IP on top of standard per-email charges
  • Virtual Deliverability Manager — no separate platform fee, but each email counts as TWO message charges when VDM is enabled (effective cost doubles to $0.20 per 1,000 emails)
  • Mail Manager — separate per-rule and per-archive pricing; typically negligible for small workloads
  • Free tier (accounts before 15 July 2025) — 3,000 message charges/month free for 12 months
  • Free tier (accounts on or after 15 July 2025) — $200 AWS Free Tier credits applicable to SES

Indian buyers pay through AWS Inc. (US entity) in USD, with 18% IGST reverse-charge for Indian B2B import — standard AWS / Indian SaaS procurement. FIRA / FIRC paperwork required for FEMA compliance on outward remittance. Note that SES is also available in the Mumbai (ap-south-1) region, which matters for latency-sensitive workloads and for some data-residency requirements (though SES specifically doesn't enforce strict residency the way some banking-data services do).

When Amazon SES is the right call

  1. You're sending high-volume transactional email (OTPs, password resets, receipts, order updates, system alerts) and the cost gap vs SendGrid / Postmark / Mailgun materially matters. At 10M+ emails/month you save ₹2–12 lakh/year vs purpose-built email APIs.
  2. You already run on AWS with IAM / VPC / CloudWatch competence — SES integrates natively into the AWS plumbing your team already operates.
  3. You want a thin email-sending rail that you wrap with your own templating / journey logic — SES is intentionally bare-bones; that's the feature, not the bug, if you have the operational capability.
  4. You operate Indian product / fintech / e-commerce / consumer-app surfaces with strict cost-economics — the per-email cost gap compounds materially with Indian send volumes (Indian D2C / fintech routinely send 5–50M emails/month).
  5. You're building an engagement platform yourself (rare for end-buyers, but common for SaaS vendors) and need a wholesale email-sending backbone — SES is the most common choice; WebEngage / MoEngage / Loops all use SES under the hood for parts of their stack.

Amazon SES is the wrong call when: you want marketing automation, drip campaigns, lifecycle journeys, segmentation, A/B testing or visual email builders — use WebEngage / MoEngage / Clevertap / Mailchimp / Loops / Customer.io which may themselves run on SES under the hood; you genuinely lack AWS-competent operations (IAM, region selection, deliverability monitoring) — Postmark's "boring works perfectly" simplicity is worth the price premium for small teams; you need visual email-builder tooling out of the box — SES has none; you specifically need a vendor that owns deliverability for you (reputation management, blacklist monitoring, list hygiene services) — Postmark / SendGrid both bundle this; or you're sending genuine marketing newsletters where engagement matters more than cost — use a newsletter platform like beehiiv / Substack / Convertkit.

Pros & cons

✓ Pros

  • Cheapest production-grade email rail — $0.10 per 1,000 emails ($0.0001/email)
  • AWS-grade infrastructure — multi-region, scales to billions of emails/day
  • Pay-as-you-go USD pricing — no minimum, no contract, no platform fee
  • Full SPF / DKIM / DMARC + dedicated IP options for high-volume senders
  • Native integration into AWS stack (SNS, Kinesis, Lambda, CloudWatch, S3)
  • Mumbai (ap-south-1) region available — meaningful for latency / data-residency
  • Backed by Amazon's own internal email infrastructure
  • Virtual Deliverability Manager + Mail Manager 2023–2024 additions modernised the stack
  • SMTP and REST API endpoints — easy to plug into existing systems
  • Free-tier mechanic generous for new AWS accounts ($200 credits post 15 Jul 2025)

✗ Cons

  • No marketing automation / journey orchestration / drip campaigns
  • No visual email builder — you bring your own templating system
  • No segmentation, A/B testing, or behaviour-based triggers built-in
  • Requires AWS-competent operations (IAM, region, monitoring, deliverability)
  • VDM doubles cost (each email counts as 2 message charges when enabled)
  • Default sandbox 200 emails/day — production access requires limit-increase request
  • USD billing through US entity — IGST reverse-charge + FIRA paperwork for Indian buyers
  • Out-of-the-box deliverability requires careful sender-reputation management
  • Built-in dashboard / analytics weak — most teams build custom on SNS / Kinesis / CloudWatch
  • Free-tier mechanic split by 15 July 2025 cutoff causes documentation confusion

Related insights & playbooks