Amazon SES SMTP settings (quick reference)
- SMTP host:
email-smtp.<region>.amazonaws.com - Ports: 25, 465, 587
- Encryption: STARTTLS or TLS
- Username: SES SMTP user (IAM‑based SMTP credentials)
- Password: SES SMTP password generated in SES console
- ✅ Auth: Authentication required (no open/unauthenticated relay)
Amazon SES pricing (at a glance)
- Sending price: about $0.10 per 1,000 emails for standard outbound traffic
- Attachments: around $0.12 per GB of attachments sent
- Free tier: up to 3,000 emails/month for the first 12 months of SES usage
- Example: 100,000 emails ≈ $10 in pure sending cost, before attachments or extras
This guide was technically verified and updated on January 23, 2026.
Amazon Simple Email Service (Amazon SES) can be turned into a cost‑effective, high‑deliverability backbone for both transactional and marketing email, as long as you pair it with the right stack and follow AWS rules on quotas, reputation and compliance. This guide walks through prerequisites, pricing, use cases, application templates, and the best tools to combine with SES.
What Is Amazon SES?
Amazon SES is a cloud email delivery service from AWS that lets you send transactional, marketing and notification emails via API, SMTP or the AWS console. It focuses on infrastructure (deliverability, scale, cost) rather than providing a rich email UI, which is why most serious senders pair SES with external software for campaigns and automation
Who Should (and Shouldn’t) Use SES?
Amazon SES shines when the sender has at least minimal technical capacity (or a dev/agency) and wants tight control over costs and deliverability.✅ It is less ideal for non‑technical users who expect a Mailchimp‑style, all‑inclusive campaign UI out of the box.❌
Ideal SES user profiles
| Use case | Why SES fits |
|---|---|
| SaaS / web apps | Cheap, scalable transactional emails (signups, resets, alerts) via API |
| Email agencies | Central infrastructure + multiple identities/domains per client |
| High‑volume senders | Extremely competitive pricing at scale vs mainstream ESPs |
| Technical marketers | Combine SES with a front‑end tool for segmentation and automation |
When SES is not a great fit
- Solo business owners needing “login and send newsletter” simplicity with minimal setup.
- Teams unwilling to manage DNS, authentication, bounces, complaints or AWS console workflows.
Prerequisites Before Applying to Amazon SES
Before you request production access, having a real, legitimate sending footprint significantly helps with approvals and future quota increases.
Technical prerequisites
- A custom domain with DNS access (for SPF, DKIM, DMARC and SES verification records).
- A functioning website or product, with pages for: signup, privacy policy, and contact/support.
- One or more monitored mailboxes for abuse@, postmaster@ or support@ to handle complaints and issues.
Business & list prerequisites
- A clear sending use case:
- Transactional only.
- Transactional + occasional newsletters.
- Agency/client work with multiple brands.
- A rough volume estimate: 50k, 100k, 500k or 1M+ emails per month (AWS often asks for both daily and monthly expectations).
- Non‑purchased, opt‑in lists, with clear unsubscribe mechanisms and documented list hygiene processes.
How Amazon SES Pricing Works (2026)
Amazon SES pricing is mostly usage‑based: you pay per 1,000 emails plus optional extras such as attachments, dedicated IPs and archiving.
Core SES pricing (sending to the Internet)
| Item | Typical pricing (reference) | Notes |
|---|---|---|
| Outbound emails | About $0.10 per 1,000 emails for standard volumes. | Volume tiers can reduce this at very high volumes. |
| Attachments (data transfer) | Around $0.12 per GB of attachments sent. | Charged on compressed size transmitted. |
| SES Free Tier | 3,000 emails/month for first year of SES usage. | After that, standard per‑1,000 pricing applies. |
Add‑ons & extras
| Extra | What it is | Pricing idea |
|---|---|---|
| Dedicated IPs | Standard or managed dedicated IP pools for higher isolation. | Billed per IP/month and/or per 1,000 emails via managed pools. |
| Email archiving | Store received emails for compliance/audit. | Example: around $2/GB ingestion + storage per GB. |
| Deliverability features | Analytics, recommendations and optional managed deliverability. | Cost depends on add‑on and region. |
Amazon SES Pricing Examples: 50k, 100k, 500k, 1M
Assumptions:
- Standard outbound email pricing of about $0.10 per 1,000 emails.
- Attachments negligible (HTML + small assets only).
Baseline sending cost examples
| Monthly volume | Formula | Approx SES send cost |
|---|---|---|
| 50,000 emails | 50 × $0.10 / 1,000 | ≈ $5 / month. |
| 100,000 emails | 100 × $0.10 / 1,000 | ≈ $10 / month. |
| 500,000 emails | 500 × $0.10 / 1,000 | ≈ $50 / month. |
| 1,000,000 emails | 1,000 × $0.10 / 1,000 | ≈ $100 / month. |
With light attachments (e.g. 50 KB average)
For 1,000,000 messages at 50 KB each, data size is roughly 50 GB per month.
| Component | Calculation | Approx cost |
|---|---|---|
| Email sends | As above | ≈ $100. |
| Attachments | 50 GB × $0.12 / GB | ≈ $6. |
| Total | ≈ $106 per month |
With dedicated IPs (example)
| Scenario | What changes | Cost effect |
|---|---|---|
| Standard shared IPs | No dedicated IP fee. | Pay only per 1,000 emails + attachments. |
| 1-2 dedicated IPs | Fixed monthly IP lease + per‑1,000 email fee for managed pools. | Increases cost but adds reputation isolation for key brands. |
Even with extras, SES typically undercuts classic ESPs by a large margin at 100k+ emails.
Key SES Features and Limits
Amazon SES is more than “just SMTP”; AWS provides strong tooling around reputation, monitoring and integration.
Core features
- Multiple sending interfaces: API, SMTP and console UI.
- Email receiving with routing to S3, Lambda or SNS.
- Reputation management dashboards, metrics and configuration sets for tagging flows.
- Support for shared, dedicated and BYOIP address ranges in some regions.
SES quotas and limits
| Limit type | Sandbox mode | Production (typical, varies) |
|---|---|---|
| Daily sending quota | Around 200 emails/day in sandbox. | Increased individually by AWS based on requests and history. |
| Max send rate | About 1 message/second in sandbox. | Gradually raised as volume and reputation grow. |
You can request higher quotas by submitting a support case (via Service Quotas or SES console) describing use case, current metrics and projected volumes.
Common Amazon SES Use Cases
Amazon SES is built to cover both application‑driven transactional traffic and campaign‑style marketing when combined with the right front‑end.
Transactional email use cases
- Account creation, welcome emails and double opt‑in confirmations.
- Password resets, security alerts and login OTP codes.
- Order confirmations, shipping notifications and billing notices.
Marketing & lifecycle email use cases
When paired with a marketing UI or automation layer, SES can handle:
- Newsletter campaigns and promotional blasts.
- Onboarding sequences, drip series and re‑engagement flows.
- Product updates and feature announcements targeted to segments.
Inbound & event‑driven use cases
- Parsing inbound email into tickets, support threads or CRMs via Lambda/S3.
- Using SNS/Lambda hooks for event‑driven workflows around bounces, complaints and engagement.
Step‑by‑Step: SES Application & Verification
Step 1, Create AWS account & choose region
- Sign up or log in to AWS, navigate to Amazon SES, and pick a region close to your main recipients (e.g. EU, US, APAC).
- Keep in mind that verified identities and quotas are region‑specific, so choose strategically.
Step 2, Verify domains and sender emails ✅
- In the SES console, add and verify your sending domain(s).
- Add the provided DNS records (TXT for domain verification, CNAME/TXT for DKIM) at your DNS host (Route 53, Cloudflare, etc.).
- Optionally verify specific emails if they will be used as from‑addresses.
Step 3, Configure SPF, DKIM and DMARC
- SPF: ensure your DNS TXT record includes SES’s sending mechanism, often via “include:amazonses.com”.
- DKIM: enable Easy DKIM in SES and publish the generated CNAMEs.
- DMARC: publish at least a basic policy (p=none) with a reporting address to monitor alignment and issues.
Step 4, Request production access (leave sandbox)
- In SES console, open Account details → Request production access (or use AWS Support).
- Provide details including:
- Types of email (transactional, marketing or both).
- Expected daily and monthly volumes.
- How you collect addresses and proof of opt‑in.
- How you manage bounces, complaints and unsubscribes.
- AWS usually responds within hours to a couple of days depending on the case.
Amazon SES Application Templates (Copy‑Adapt)
Below templates map to queries like “how to fill Amazon SES production access form” and “SES production access request example”.
Template 1, Pure transactional SaaS
We operate a SaaS platform that provides [brief description].
We will use Amazon SES strictly for transactional emails, including account registration confirmations, password reset emails, security notifications and usage alerts.
All recipients have explicitly created an account in our application, and we do not send emails to purchased or third‑party lists.
Unsubscribe or notification preference management is available within the application for non‑essential messages.
We monitor bounces and complaints through Amazon SNS/webhooks and automatically suppress problematic addresses to maintain list hygiene.
Template 2, Transactional + low‑frequency newsletters
In addition to transactional messages, we send low‑frequency newsletters (1-2 per month) to users who have opted in through our website.
Content includes product updates, educational resources and relevant promotions related to our service only.
Each email includes a clear unsubscribe link, and we promptly honor all opt‑out requests.
We store proof of sign‑up (time, IP, source) and never send emails to purchased or rented lists.
Bounces and complaints are tracked via SNS/webhooks, and affected addresses are suppressed automatically.
Template 3, Agency / multi‑tenant sending
We manage email communications for multiple client brands as a digital agency.
Each client uses their own sending domain and verified identities in Amazon SES.
We only send to lists collected via explicit opt‑in through our clients’ websites, CRM systems or offline processes with clear consent.
We centrally enforce unsubscribe and complaint handling across all clients and automatically remove hard bounces and high‑complaint sources from our system.
We monitor sending statistics by domain and client to ensure compliance with AWS policies and industry best practices.
Deliverability & Compliance Best Practices on SES
Good deliverability is mandatory if you want SES to keep raising your limits and avoid throttling or blocking.
Authentication & reputation
- SPF, DKIM and DMARC properly configured and aligned between visible From and envelope domains.
- Gradual warm‑up when starting or after long inactivity to avoid sudden volume spikes on fresh IPs or domains.
- Keep hard‑bounce rates well under 2% and complaint rates well under 0.1% to stay in safe ranges.
Handling bounces, complaints and unsubscribes
- Use SNS or webhooks to capture bounces and complaints and suppress those addresses automatically in your sending system.
- Include a one‑click unsubscribe link in marketing emails and honor it immediately.
- Avoid purchased, scraped or co‑registration lists to remain compliant with AWS acceptable use policies.
Integrating Amazon SES: SMTP vs API
Choosing between SMTP and API is a key architectural decision when connecting SES to your app or email platform.
SMTP vs API overview
| Aspect | SMTP integration | API integration |
|---|---|---|
| Setup | Simple: hostname, port, username/password. | Requires integration with AWS SDK or HTTPS calls. |
| Performance | Good for moderate volume; limited control over batch sending. | Better for high volume, parallelization and complex workflows. |
| Error handling | SMTP status codes; harder to correlate at scale. | Structured responses and granular status via SDKs. |
| Event tracking | Often via SNS → app. | Deep event hooks and programmatic routing. |
When to choose which
- SMTP: great for connecting existing tools like MailWizz, Mautic, Sendy or WordPress plugins quickly.
- API: ideal for in‑house apps and SaaS platforms needing precise control, advanced error handling, dynamic templates and clean scaling.
Self‑Hosted Email Apps That Work with SES
Self‑hosted tools give you ownership and flexibility while SES handles delivery, reputation and scaling.
Typical self‑hosted stack with SES
| Tool category | Example tools | Role with SES |
|---|---|---|
| Bulk email / newsletters | MailWizz, Sendy, Mautic | Campaigns, lists, templates, schedules. |
| CRM + email | SuiteCRM, custom CRMs | Automations + transactional campaigns via SES SMTP/API. |
| WordPress plugins | Newsletter plugins, WooCommerce add‑ons | Transactional + marketing emails powered by SES. |
These tools usually configure SES either as an SMTP server or, when supported, via SES API keys for better performance and tracking.
Cloud Email Platforms That Sit on Top of SES
Cloud platforms abstract SES complexity and ship with UX that marketers love, while preserving SES‑level deliverability and pricing.
Examples of SES‑centric cloud tools
| Platform type | Example | What it adds on top of SES |
|---|---|---|
| SES‑based email marketing | BigMailer | Central UI, list management, campaigns and deliverability tools. |
| Marketing automation / CRM | Agile CRM, MailSend | Automations, workflows, forms, lead management + SES integration. |
| Campaign management platforms | CampaignHQ‑style tools | Multi‑brand sending, reports and pricing visibility on top of SES. |
These platforms typically handle SES integration, SNS queueing for bounces/complaints, scheduling, user management and sometimes IP/warm‑up strategies, letting you stay “on SES” without babysitting AWS directly.
Example Stacks: From Zero to Sending
This section maps nicely to queries like “best stack with Amazon SES for SaaS” or “how to use Amazon SES with MailWizz”.
Stack 1, Small SaaS product
- App: your web app or backend service.
- Email backbone: Amazon SES via API.
- Flow: app calls SES SendEmail/SendTemplatedEmail for signups, resets, notifications; CloudWatch and SNS monitor delivery and errors.
Stack 2, Newsletter‑first business
- UI: MailWizz / CampaignHQ‑type platform.
- Delivery: SES via SMTP or API.
- Flow: lists, campaigns and automations managed in UI; SES handles send, while bounces and complaints route via SNS into the app or an external suppression store.
Stack 3, Agency / multi‑brand setup
- Central platform: multi‑tenant email marketing UI (self‑hosted or SaaS).
- Infrastructure: one AWS account with multiple SES identities per client domain.
- Flow: each brand sends using its own verified domain and configuration set; the agency monitors overall reputation, quotas and IP usage from SES dashboards.
Monitoring, Analytics and Scaling with SES
Monitoring & analytics
- SES console: sends, bounces, complaints, rejections and reputation metrics per identity and configuration set.
- CloudWatch dashboards: send rates, delivery status, failures and latency for deeper observability.
- SNS: event notifications for bounces, complaints and engagement, feeding your suppression logic and analytics layer.
Scaling to higher volumes
- Warm up gradually (e.g. 1-3k/day → 10k/day → 50k/day) to avoid shocking ISPs and SES with sudden spikes.
- Request quota increases proactively when you are consistently near your daily limits, providing historical metrics and forecasts in your request.
- Consider dedicated or managed IPs once you are sending substantial volume and want strict isolation for premium brands or critical mailstreams.
Pros, Cons and Alternatives to Amazon SES
Pros ✅
- Extremely low cost at all scales, especially compared to classic ESPs at 100k+ emails.
- Deep integration with AWS (Route 53, S3, Lambda, CloudWatch) for automation and analytics.
- Flexible integration patterns (SMTP/API/console) and IP options (shared, dedicated, BYOIP).
Cons ❌
- Console/UI is infrastructure‑oriented, not marketer‑friendly without an external app.
- Requires DNS configuration, event handling and basic deliverability knowledge to unlock full potential.
- Support and approval processes can be strict for borderline use cases like cold outreach or aggressive promotions.
High‑level comparison table
| Feature | Amazon SES | Full ESP (e.g. Mailchimp/SendGrid) |
|---|---|---|
| Pricing at 100k emails | ~$10/month for sending only. | Often $50-$400+ depending on plan. |
| UI & templates | Basic (needs external tools). | Rich editors, flows and templates by default. |
| Technical skills required | Moderate to high. | Low to moderate. |
| Deliverability control | High with correct setup and monitoring. | Good but more black‑box to the end user. |
Amazon SES FAQ
Is Amazon SES good for cold email?
Amazon SES is not designed for cold email and AWS policies strongly discourage sending to non‑opt‑in lists. Using SES for cold outreach significantly increases your risk of account restrictions or termination and can damage long‑term deliverability.
Do I need dedicated IPs for Amazon SES?
Most senders do not need dedicated IPs initially; SES shared IPs work well when your reputation and list quality are good. Dedicated or managed IPs make sense once you send consistent high volume or need strict reputation isolation for critical brands or traffic types.
Can I use Amazon SES for multiple domains and brands?
Yes, you can verify multiple domains and identities in one SES account and send on behalf of different brands, provided each domain is verified and compliant. Agencies usually combine this with per‑brand configuration sets, custom return‑paths and separate monitoring to keep reputations clean.
How do Amazon SES quotas and max send rates work?
Every SES account has a daily sending quota and a maximum send rate, both enforced on a rolling 24‑hour basis. When you approach these limits, SES starts throttling or rejecting additional send attempts until the window frees up or AWS approves a higher quota.
Is Amazon SES reliable for transactional emails?
Amazon SES is widely used by SaaS products and large applications for high‑priority transactional traffic due to AWS’s global infrastructure and robust deliverability tooling. When authentication, list hygiene and monitoring are in place, SES is highly reliable for mission‑critical messages.
About the Author
Alaa · LinkedIn
Email infrastructure specialist with 8+ years of hands-on experience in SMTP, deliverability, and email verification. I’ve configured and troubleshot mail systems across Postfix, Exchange, and cloud relays, managed IP reputation and warmup campaigns, and built verification pipelines processing millions of addresses. My work spans DNS authentication (SPF, DKIM, DMARC, BIMI), bounce handling, blocklist monitoring, and compliance frameworks including CAN-SPAM and GDPR. I write every article on SMTPedia to give email professionals, developers, and marketers the accurate, RFC-grounded reference they need.
About SMTPedia
SMTPedia is an independent email industry reference covering SMTP, IMAP, POP3, email deliverability, marketing platforms, DNS authentication, and email verification. Every article is researched from official provider documentation, IETF RFCs, and industry best practices. Settings and configurations are verified quarterly.
We are cited as a source by ChatGPT, Microsoft Copilot, and thousands of email professionals worldwide. Learn more about our editorial process.
