Route 53 DNS Migration
A zone moved with every record accounted for, and the TTLs lowered before the change rather than after.
From $199 1–2 days
Amazon SES & Email Deliverability
Application mail that arrives, with bounces handled before they cost you the account.
Price and scope
From $299
Typically $299–$649, fixed in writing before anything starts.
What moves it up
- Leaving the sandbox, which is a request AWS can refuse and which has to be argued properly
- An existing reputation problem, where the work starts below zero rather than at it
- Sending from more than one domain or subdomain, each needing its own identity and alignment
Some of this you can check yourself, right now, for free: Email Domain Health Check →
What actually goes wrong
SES behaves impeccably in the sandbox, because in the sandbox you can only mail addresses you own. Production sending is where it turns, and it turns on bounces: AWS watches the bounce and complaint rate, and an application that keeps sending to addresses which reject it will have its sending paused — not throttled, paused. The quieter failure is alignment. SPF passes, DKIM passes, and DMARC still fails, because the domain DKIM signed with is not the domain in the From header, and nothing in either individual check notices that.
How I find it
aws sesv2 get-account --query '[ProductionAccessEnabled,SendingEnabled]'aws sesv2 get-domain-statistics-report — the actual bounce and complaint rates, not an estimateA real message sent to a mailbox, with the Authentication-Results header read for all three of spf, dkim and dmarcdig TXT _dmarc.<domain> and the DKIM selector, checked for alignment with the From domain
What you get
- A verified domain identity with DKIM signing that aligns with the address you send from
- SPF, DKIM and DMARC agreeing, verified by reading the headers of a message that actually arrived
- Bounce and complaint notifications routed to somewhere that suppresses the address automatically
- A configuration set with event publishing, so deliverability is a metric rather than an anecdote
- The production access request prepared and submitted with the detail AWS asks for
Questions
How long does it take to get out of the SES sandbox?
AWS usually answers within a day or two, and they can say no. The request has to describe what you send, to whom, how they opted in and what happens on a bounce — a thin answer gets refused, and a refusal is slower to recover from than doing it properly the first time.
Should I use SES instead of a service like Postmark or SendGrid?
SES is dramatically cheaper and gives you less. No dashboard worth the name, no templates to speak of, and you handle suppression yourself. For transactional mail at volume from an application already on AWS, it wins. For a marketing team who need to see what happened, it does not.
My email already works. Why would I need this?
It works until a chunk of it silently stops, which is what deliverability failure looks like — not an error, just fewer people replying. If your Authentication-Results header shows dmarc=pass on a real received message, you probably do not need me.
Can this fix mail that is already landing in spam?
It can fix the technical causes, which are the ones worth fixing first and are usually the whole problem for application mail. It cannot undo a reputation earned by sending to a purchased list — that recovers with time and behaviour, not configuration.
If this is not quite it
Website / Application Migration to AWS
Moved onto AWS with the cutover rehearsed, the DNS planned, and the old host still standing.
From $459 2–5 days
Want this done?
Tell me what you are running and I will come back with a fixed price and a date. If it turns out you do not need this, I will say that instead.
Prefer to talk? Book a free call ↗ · Or hire me on Upwork ↗ · Typical reply within one business day.
Before you enquire
When I answer
Sunday to Thursday, 09:00–18:00 EET. Outside that I will still look, but I will not promise a time.
No 24/7 desk, and I will not pretend otherwise
One person, one time zone. If round-the-clock cover is what you need, you need a team, and I will say so rather than sell you a plan that cannot deliver it.
Your AWS bill stays yours
You pay Amazon directly and you keep control of the account. Nothing here resells your infrastructure or sits between you and your own billing.
A price that starts with "from" is a starting price
Every service page lists exactly what pushes a quote above it, before you ask. You get a fixed number in writing before any work begins.