Amazon SES Setup for Deliverability: Configuration Guide

Why Teams Choose Amazon SES

Amazon SES is the most cost-effective ESP for teams that send at scale. At $0.10 per 1,000 emails (with no monthly base fee if you're already on AWS), it's dramatically cheaper than alternatives like SendGrid ($20-90/month) or Mailgun ($35-80/month) at high volume.

The tradeoff: SES gives you raw sending power with minimal hand-holding. You're responsible for your own authentication, bounce handling, and reputation management.

Initial Setup

Bounce and Complaint Handling

This is where most SES users make critical mistakes. SES requires you to handle bounces and complaints — if you don't, they'll suspend your account.

How to set up notifications:

1. Create an SNS topic for bounces and another for complaints
2. In your SES configuration set, add SNS as the event destination for Bounce and Complaint events
3. Build a handler (Lambda function or webhook endpoint) that processes these notifications and updates your suppression list

Monitoring SES Health

SES provides a reputation dashboard showing your bounce rate, complaint rate, and overall account health. However, this data is limited to SES's perspective — it doesn't tell you about inbox placement or Gmail-specific reputation.

Key metrics to monitor in SES:

• Bounce rate — Keep below 3% (SES pauses at 5%)
• Complaint rate — Keep below 0.05% (SES warns at 0.08%, pauses at 0.1%)
• Send rate — Monitor for throttling or delivery delays

What SES doesn't tell you (without VDM):

• Whether emails landed in inbox vs spam
• Your domain reputation at Gmail, Outlook, or Yahoo
• Engagement metrics like open and click rates — SES only exposes these via the VDM API (BatchGetMetricData). If VDM is not enabled, engagement data is only available through real-time SNS notifications.

With VDM enabled, SES provides daily aggregate open/click counts accessible via the API. Boxset uses this data to display accurate engagement metrics in your dashboard, backfilling up to 14 days of historical data on every sync.

This is where connecting Boxset fills the gap — pulling SES health data, VDM engagement metrics, Google Postmaster reputation, and blacklist monitoring for a complete picture.

Common Pitfalls

1. Ignoring sandbox mode — Test emails work fine, but you'll wonder why production sends fail until you request production access.
2. Not setting up bounce handling — SES will suspend your account if bounce rates exceed 5%. This happens faster than you think with a stale list.
3. Sending from the wrong region — SES endpoints are regional. Use the region closest to your recipients for best latency, and ensure your application is configured for the correct region.
4. Missing custom MAIL FROM — By default, SES uses a generic amazonses.com MAIL FROM domain. Set a custom subdomain (e.g., mail.yourdomain.com) for better authentication alignment.
5. Not enabling VDM — Without Virtual Deliverability Manager, open and click rates show as 0% in third-party tools like Boxset. The SES console shows engagement data internally, but it's not available via the public API without VDM enabled.

Frequently Asked Questions