Lead Piranha

Professional Services · 6 min read

Amazon SES Application Denied: What We Fixed

Our Amazon SES application denied us production access in June. Here is what Amazon checks, what we rebuilt, and what sending really costs.

LVLouie Villaverde
Three-column table comparing weak SES application answers with strong specific detailed responses

If you have a few thousand past clients on a list, most email platforms charge you by the head. Import your dormant client file and the bill climbs again, whether those people ever open a send or not. Amazon SES charges by the send instead, which is why so many small firms try to move there and then hit a wall at the application screen.

We hit that wall in June. So here is what got our Amazon SES application denied, and what we changed to send our own newsletter on the second try.

Three things worth your ten minutes: what Amazon actually reads when it reviews an account, what the denial looks like when it lands in your inbox, and the setup that has to be live before you apply. Then the real cost of sending once you're through.

Why Was Our Amazon SES Application Denied?

Amazon denied our production access because the application described a plan instead of a working system. We named a newsletter, but our sending domain, authentication records, and bounce handling were not finished yet. SES reviewers approve accounts that can already prove where the mail comes from and what happens when a send fails.

The denial itself was short and almost useless. There aren't any line items. No "fix this and resubmit." Just a note that they could not grant production access based on the information provided, with an invitation to reply with more detail.

That vagueness is the part that trips people up. You read it as rejection, open a second AWS account, and start over. Sending nothing is the worst move you can make here.

Here is what was actually wrong on our first pass. We asked to send from the root domain, which mixes newsletter mail in with the mail our team sends by hand. Our authentication records were half done. There was nowhere for bounces and complaints to land. And our use case was one sentence long, something close to "marketing emails to our list."

Quick win: reply in the same support case rather than starting a new one. The reviewers can see your old answers, so a better answer reads as progress instead of a fresh stranger asking again.

A denial is not a ban

Production access is a review, not a verdict on your business. You can re-apply as many times as you need to in the same case. What you cannot do is open a second AWS account to dodge the review, which is the fastest way to get both accounts suspended.

What Amazon Checks Before It Grants Production Access

Strip away the form fields and the review comes down to one question: if we let this account send, who pays for the complaints?

So the reviewer is looking for proof that you know your list, that people chose to be on it, and that your system removes anyone who bounces or complains without a human remembering to do it. Amazon's own guide to requesting production access says this plainly, and the detail it asks for is not decoration.

For a law firm, an accounting practice, or an advisory shop, this part is easier than you think. Your list is real clients who hired you. Your sign-up path is a form on your own site. Your content is a monthly letter, not blasts to a purchased file. You just have to say it that way, with specifics.

The second application we sent was built from the same setup checklist we use for client email builds. Same fields, longer answers, every claim backed by something already live.

Our first SES application versus the rebuilt one
What Amazon asksA thin answerWhat we sent the second time
Who receives your mailOur subscribersClients and past clients who opted in through two named forms on our site
How they signed upNot mentionedDouble opt-in with confirmation, and the confirmation copy pasted into the case
What you sendMarketing emailsOne weekly letter plus transactional receipts, with sample subject lines
How people unsubscribePlatform defaultOne-click link in every send, suppressed in our own database within seconds
What happens to bouncesLeft blankBounces and complaints posted to a webhook that suppresses the address automatically

The Setup That Has to Be Live Before You Apply

None of this is hard. It is just a list, and it has to exist before the review, not after.

Sending subdomain and email sending domain setup

We moved all newsletter sending to a dedicated subdomain. Mail your team types by hand stays on the root domain. That way a bad week on the newsletter never follows your partner's reply to a client into the spam folder.

Then three records: Easy DKIM so Amazon signs your mail, a custom MAIL FROM so bounce reports come back to your own domain, and an SPF record that lines up with both. If you have never looked at these, we walked through how to check your domain's three email records in about ten minutes.

Bounce and complaint handling that runs without you

This is the piece most applications are missing. A configuration set collects the events, and those events have to go somewhere that actually acts on them. Ours post into Mautic, which suppresses the address on a hard bounce or a complaint and never tries it again.

Write that sentence into your application. "Bounces and complaints are suppressed automatically in our own database" does more for you than three paragraphs about your content calendar.

We break down how we wire this into the rest of a client's system in our full process overview, including who owns the list once it is built.

One more thing worth saying out loud: your sending setup is plumbing, not permission. You still owe your readers the CAN-SPAM basics the FTC spells out, and if you are an attorney, your state bar's advertising rules still apply to every letter you send.

The Lead Piranha Playbook

You're doing the work of a team you don't have.

Every Tuesday I show you one job I automated for good. What it does, the tools by name, and the prompt to copy.

No spam, unsubscribe anytime.

What Does It Cost to Send Your Own Newsletter Through SES?

Published SES pricing is $0.10 per 1,000 emails sent, with no charge for storing contacts. Mailing a 10,000-person list costs a dollar. Mailing it four times a month costs four dollars.

Compare that to per-contact pricing, where the same 10,000 names cost the same every month whether you send or not. We put real numbers on that gap in our breakdown of email marketing cost per contact, and for firms with long client lists and slow decision cycles, the gap is most of the bill.

There are two honest caveats worth naming. You are now responsible for your own deliverability, your own templates, and your own suppression logic, which is real work. And SES sends mail; it does not write it, segment it, or decide who should hear from you this month.

Quick win: price it before you move. Take your current platform bill, divide by your actual monthly send volume, and compare that to a dime per thousand. If the difference is under fifty dollars a month, stay where you are.

$0.10
Per 1,000 emails sent
AWS published SES rate
$1.00
To mail a 10,000-person list once
Same price again next month
$0
Per contact stored
You pay to send, not to keep

Should You Build This Yourself?

If you have one list, one letter, and someone technical in the building, yes. The setup is a few hours and the review is a few days.

If your contacts are scattered across a practice management tool, an old email platform, and two spreadsheets, the sending account is not your problem yet. Fix the list first. We wrote about what that migration actually involves when switching CRM systems, because the cleanup is always bigger than the move.

And if you have been denied already, read your own answers back as a stranger would. Ours read like intentions. The approved ones read like a description of something already running.

Quick Growth Check

5 questions. 30 seconds. Find out where your growth system stands.

Sending Your Own Client Newsletter Without the Per-Contact Bill

Our second application cleared because the setup existed before we asked. That is the whole lesson from what got our Amazon SES application denied, and what we changed to send our own newsletter after it.

If you want the sending domain, the authentication records, the suppression logic, and the letter itself built as one system instead of five separate afternoons, book a 30-minute call and we will map it against the list you already have.

Next up in this thread: the warm-up schedule we run in the first thirty days after approval, and why sending your whole list on day one undoes all of this.

Share:LinkedInPostThreads

Related articles

See what's worth building

Tell us about your business, and we'll find the work a system could take off your plate.

Apply now
  1. Apply

    Three short steps about you and your business.
  2. Hear back right away

    If it's a fit, you can book an intro call right on the spot.
  3. The Diagnostic

    After the call, a full consult with you and your team, refunded if we find nothing worth building.