Sending with Amazon SES?

Amazon SES bouncing, throttled or stuck in sandbox? We fix it.

SES is the cheapest reliable way to send transactional email at volume, and the quickest way to get blacklisted if you do not watch the bounce rate for the first week. We walk through the sending identity, the DKIM records, the suppression list and the CloudWatch metrics until throttling makes sense and your Gmail inbox-placement test lands on time.

  • Since 2015Fixing technology
  • FreeEstimates
  • US teamReal engineers

ses-send.log

still broken

What it is

Amazon SES at a glance

Amazon Simple Email Service (SES) is AWS's transactional and marketing email service, launched in 2011. It offers SMTP and an HTTP API for outbound mail, inbound receiving for a handful of regions, bounce and complaint feedback via SNS, and reputation metrics in CloudWatch.

Pricing at ten cents per thousand emails makes it the cheapest serious sender in the cloud, with the catch that AWS expects you to manage sending identity, bounces and complaints yourself. New accounts land in a sandbox restricted to verified recipients, and request a production move only after a short review.

Type
Transactional and bulk email service
First released
2011
License
Proprietary, usage-based pricing
Maintained by
Amazon Web Services
Typically used for
Transactional email, receipts, password resets, bulk marketing sends via AWS

The honest version

Amazon SES pros and cons

No technology is all upside. This is where Amazon SES earns its place and where it tends to cause trouble.

Where Amazon SES is strong

  • Very cheap at volumeTen cents per thousand outbound messages is hard to match. For receipts and password resets, the per-send cost rounds to zero.
  • Deep AWS integrationIAM, SNS, CloudWatch, EventBridge and Lambda all connect natively. Bounces, complaints and delivery events flow into the same pipelines as the rest of the stack.
  • Configuration sets are powerfulPer-stream reputation metrics, event destinations and IP pools let you separate marketing, transactional and system traffic cleanly.
  • Dedicated IPs if you need themFor high-volume senders, a dedicated IP or Managed IP pool gives you control over reputation rather than sharing it with a crowd.
  • Honest documentationThe developer guide covers the real behavior of throttling, suppression and feedback; it does not hide the gotchas the way vendor marketing does.
  • Inbound receiving in US regionsFor teams that need programmatic inbound mail, SES can receive and drop into S3, SNS or Lambda, with Receipt Rules controlling the flow.

Where Amazon SES bites

  • You are the deliverability teamSES will send what you ask. Watching bounces, complaints and engagement, and throttling your own code when reputation drops, is on you.
  • Sandbox is mandatory and manualEvery new account starts restricted to verified recipients and needs a request to leave the sandbox. The approval is human-reviewed and can take a day.
  • No ESP features out of the boxThere is no template management UI, no A/B testing and no engagement reporting beyond the basics. Teams either build it or layer a tool on top.
  • Account suspensions are opaqueA spike in bounces or complaints can get sending paused at the account level, and the path back is a human review that may take days.
  • DKIM setup has sharp edgesEasy DKIM, custom MAIL FROM and BYODKIM each have their own set of DNS records and their own ways of silently failing alignment on Gmail.
  • Per-region quirksSending quotas, available features and suppression behavior vary between regions. Running in us-east-1 is not the same experience as eu-west-1.

Sound familiar?

Common Amazon SES problems we fix

The Amazon SES problems that bring people to us, and what you have once each one is fixed.

AccountSendingPausedException

SES pauses sending after a bounce spike

A bounce rate above the AWS threshold, a complaint rate climbing fast, or a single bad campaign to very old recipients that turned reputation negative.

Account back in good standing

MessageRejected: identity not verified

Mail fails because the sending identity is not verified

A domain whose DKIM CNAMEs were never added, an SPF record missing the ses sending block, or a verification that lapsed because the domain was transferred.

Identities verified and alignment passing

Throttling: Maximum sending rate exceeded

Bulk sends hit the per-second limit

A batch job that dispatches at full speed without respecting the SES rate, or a campaign that forgot to request a quota raise before launch.

Sends paced within the quota

DKIM authentication failed at Gmail

Gmail rejects DKIM alignment

A body-hash mismatch caused by a mail relay rewriting the message, or a selector that points at the wrong key after a BYODKIM rotation.

DKIM aligns and passes on inbox providers

SMTP 554: Email on suppression list

Specific recipients never receive mail

An address on the account-level or global suppression list after a prior bounce or complaint, blocked until explicitly removed.

Suppressions reviewed and cleaned

MailFromDomainNotVerified

A custom MAIL FROM domain is not verified

MX and TXT records pointing at the wrong feedback smtp endpoint, or a subdomain the team expected to inherit records from the parent.

Custom MAIL FROM live and aligned

ConfigurationSetDoesNotExist: 'prod'

A send references a missing configuration set

A deployment where the configuration-set name differs between environments, or a config set that was deleted before an archived job stopped referring to it.

Config sets consistent across environments

Complaint rate approaching 0.3 threshold

Complaint rate is close to the pause threshold

A marketing send that reused a list from a different context, or a lifecycle email whose unsubscribe link was broken for several days.

Complaint rate reduced, lists cleaned

What we do

Amazon SES help, from rescue to upkeep

Reach out for one paused account, or hand us the whole transactional email setup.

Rescue
Account paused, DKIM failing at Gmail, or production stuck in sandbox. We stabilize the sending path first and document what changed second.
Sandbox exit and quota raises
Preparing the production access request and quota increases with the information AWS needs to approve them on the first pass.
Authentication and reputation
SPF, DKIM, DMARC, custom MAIL FROM and BYODKIM set up so alignment passes on every major inbox provider.
Configuration sets and event pipelines
Event destinations into SNS, Kinesis Firehose and warehouse tables so bounces, complaints and deliveries become data you can act on.
Migration
Moves from SendGrid, Mailgun, Postmark or SMTP on an EC2 instance onto SES without losing deliverability.
Managed Tech
CloudWatch dashboards, bounce and complaint watchers, suppression reviews, and a US engineer on call when reputation slips.

How it works

From first message to fixed

  1. Look Free estimate

    Tell us what's going wrong. We look at it, then tell you plainly what's wrong and what it will cost.

  2. Fix

    We fix the cause, not the symptom. If something is down, getting it back up comes first.

  3. Harden

    Backups, monitoring, updates and access, so the same problem can't quietly come back.

  4. Hand back or stay on

    You get a plain-language write-up. Or we stay on for hosting, upkeep and new work.

Often found together

Running Amazon SES alongside something else?

We work on the whole stack, so the problem can be wherever it actually is.

Questions

Amazon SES questions

Something else? Call+1 737 727 7327

Why is my Amazon SES account paused?

The common causes are a bounce rate above the AWS threshold, a complaint rate climbing past the warning line, or a specific campaign that drew enough complaints to tip the account. The fix is to remove the offending sends from the schedule, clean the list that produced the bounces, and respond to the AWS reinstate request with specifics about what will change.

How do I get out of the SES sandbox?

Request production access from the SES console with a short description of what you send, where the recipients came from and how you handle bounces and complaints. Specific answers are approved; vague ones are declined. If the account is also new to the AWS region, expect the review to take a business day.

Why is Gmail silently spam-foldering our SES mail?

The usual suspects are a DKIM key that passes but does not align with the From domain, SPF that lists the right includes but a Return-Path pointing at a domain without alignment, and content that reads like marketing to Gmail's filters. Fixing alignment, warming up the sending domain gradually and tightening list hygiene almost always recovers it.

Should we use SES over SendGrid or Mailgun?

For raw cost at volume and deep AWS integration, SES wins. For teams that want template management, inbound parsing, analytics and a UI for non-engineers, SendGrid or Mailgun pay for themselves in reduced tooling. Many teams run SES for transactional and a dedicated ESP for marketing.

How do we handle bounces and complaints programmatically?

Route SES notifications through SNS to an SQS queue or a Lambda function, land the events in a database and a warehouse, and act on bounces at the identity level. We build the pipeline and the suppression hygiene so bounce rate stays below the AWS threshold without ongoing manual work.

How much does Amazon SES help cost?

The quote is free. Send over the sending volume, the current bounce and complaint rates and any pending AWS messages, and we come back with a fixed price before any production change happens.

Free estimate

Amazon SES giving you trouble?

Share the sending identity, the volume and any AWS warnings, and a Hawkins.Tech engineer replies with an estimate.

  • No charge to find out what it will take
  • If it's urgent, say so

Replies come from a person. By sending, you authorize us to email you back. No marketing.