All Services

Business Apps

Amazon Simple Email Service

Amazon Simple Email Service sends and receives application email through regional APIs and SMTP, with verified identities, DKIM and custom MAIL FROM, configuration sets, deliverability and reputation metrics, event destinations, suppression, dedicated IP options and Mail Manager.

Explore pricing models, common use cases, infrastructure support, and the AWS services that commonly work with Amazon Simple Email Service.

Amazon Simple Email Service pricing and cost programs

Pricing model: Email message and data usage

On-Demand
Available
Reserved Instances or reserved capacity
Not applicable
Savings Plans
Not applicable
Spot
Not applicable

Billing dimensions: Messages sent or received · Data volume · Dedicated IPs · Mail Manager

Programs and modes: Outbound and inbound email · Virtual Deliverability Manager · Dedicated IPs · Mail Manager

Message source, attachments, data transfer, deliverability features, and dedicated IP choices affect charges.

Free Tier: Available — verify current offers

Pricing reviewed 2026-07-25. Reviewed against the linked official AWS pricing page. Recheck regional rates and program terms before purchase.

Official AWS pricing

Official AWS sources reviewed 2026-07-21.

Why implement Amazon Simple Email Service?

  • Replaces outbound mail-transfer-agent fleets and much scaling, queueing and ISP connectivity work with a usage-based regional service.
  • Supports API and SMTP sending, receiving, templates, bulk and transactional mail, dedicated IP pools, tenants, configuration sets and event publishing.
  • Provides identity verification, DKIM, custom MAIL FROM, deliverability dashboards, account and tenant suppression, reputation metrics and bounce or complaint feedback.

How to implement Amazon Simple Email Service

  1. Separate transactional and marketing streams, define consent and unsubscribe behavior, sending domains, Regions and recovery, message data classification, templates, quotas, volume ramp, feedback owners and retention.
  2. Verify domain identities in every sending Region, enable Easy DKIM or controlled signing, configure custom MAIL FROM with SPF and a staged DMARC policy, request production access, and grant applications only `ses:SendEmail` or the minimal required actions.
  3. Attach configuration sets with delivery, bounce, complaint, reject and delay events, enable suppression and reputation monitoring, process feedback idempotently, warm volume gradually, test rendering and authentication, and stop problematic campaigns quickly.

Amazon Simple Email Service best practices

  • Use domain identities with DKIM, aligned SPF or custom MAIL FROM, and DMARC; start DMARC in monitor mode, inspect reports, then move to quarantine or reject only after every legitimate sender aligns.
  • Send only expected and consented mail, provide working unsubscribe paths, isolate transactional from marketing reputation, never retry permanent bounces, suppress complaints immediately, and monitor feedback by configuration set or tenant.
  • Keep SMTP credentials and API roles out of source, use least privilege and rotation, remember identities and many settings are Regional, ramp new domains and dedicated IPs gradually, and validate a multi-Region recovery plan before relying on it.

Amazon Simple Email Service use cases and server impact

  • Transactional account and order email
  • Opt-in marketing and lifecycle campaigns
  • Inbound email processing and application notifications

Replaces outbound and inbound mail-server fleets and much deliverability telemetry, while consent, content, authentication DNS, credentials, bounce and complaint handling, sender reputation, regulatory compliance and regional recovery remain yours.

Official implementation resources

Commonly paired AWS services