# SES Production Access Request Builder Source: https://wraps.dev/tools/ses-production-access ![Wraps Logo](https://wraps.dev/wraps-light-logo.png)![Wraps Logo](https://wraps.dev/wraps-dark-logo.png) ](https://wraps.dev/) [](https://github.com/wraps-team/wraps)[Log in](https://app.wraps.dev/auth?mode=signin)[Sign up](https://app.wraps.dev/auth?mode=signup) Toggle menu wraps · free tool # SES production access, written out AWS asks for an email type, a website and a contact address, then decides from that whether to trust you with everyone's inbox. This builds the text that answers what the form left out — and if you have already been refused, it matches the refusal against the four gaps that cause most of them. Everything runs in your browser. No account, nothing uploaded, no AI writing on your behalf — the templates are fixed, because this goes to AWS support under your name. ## Why requests get denied The refusal AWS sends names nothing: “we reviewed your request and determined that your use of Amazon SES could have a negative impact on our service.” It reads as a judgment of you. It is closer to a judgment of the form, which did not have room for any of this. Denials cluster into four gaps. No verified domain A request from an account that has only verified a single email address gives AWS nothing to check. - Verify the sending domain in SES, not just one address. - Enable DKIM signing and wait for the status to leave Pending. - Publish SPF and DMARC records for the same domain. The website does not explain the mail A parked domain, a landing page with no signup form, or a URL that does not match the sending domain. - Put the signup form, or the product the mail comes from, on a page a reviewer can reach without an account. - Publish a privacy policy that says what you do with an email address. - Use a website URL on the same domain you send from. No opt-in story Nothing in the request says how recipients ended up on the list. - Write down, in one sentence, how an address gets onto the list. - Say plainly that you do not buy, rent or scrape lists. - If the list predates the form, say when and how those addresses were collected. No bounce or complaint handling The acknowledgement box says you have a process. AWS wants to know what it is. - Subscribe to bounce and complaint events — an SES event destination or a webhook, not a mailbox nobody reads. - Remove hard bounces and complaints from the list automatically, and keep them suppressed. - Honor unsubscribe requests immediately, and carry List-Unsubscribe headers on bulk mail. Fix the gap before you reply, not after. A reply describing a process AWS cannot see on your site or in your account does not help your case — the reviewer checks. The full walkthrough, including how to read the review status from the CLI, is in the [production access guide](https://wraps.dev/docs/guides/production-access). ## The bounce pipeline is the gap you cannot write your way out of Three of the four gaps are things you write down. The fourth is a thing that has to exist. Wraps deploys the bounce and complaint pipeline and the suppression list into your own AWS account during `wraps email init`, so the paragraph above describes something real. [Start free](https://app.wraps.dev/auth?mode=signup)[Bounce handling](https://wraps.dev/docs/guides/bounce-handling) Not submitted yet? Work through the [16-point pre-request checklist](https://wraps.dev/blog/ses-sandbox-guide#pre-request-checklist) first — it is free, it ticks off as you go, and most refusals are something on it that was skipped. ## Frequently asked questions Why did AWS deny my SES production access request? The request form asks for an email type, a website and contact addresses, so reviewers have to infer your sending practices from very little. Denials cluster into four gaps: the account has verified a single email address rather than a domain; the website does not explain the mail; nothing says how recipients ended up on the list; and there is no bounce or complaint handling. The standard refusal — that your use of Amazon SES could have a negative impact on our service — names none of them, which is why it feels arbitrary. What should I write in an SES production access request? Answer the four questions the form never asks, in plain sentences: what you send and what triggers it, how an address gets onto your list, roughly how many emails you expect to send, and what happens to a bounce or a complaint. Name your unsubscribe mechanism. Keep it short and specific — a paragraph of detail a reviewer can check against your site beats a page of intent. Can I appeal an SES production access denial? Yes. A denial is not final. AWS delivers the decision through a Support Center case tied to your request, and that case is where you reply with more detail. Fix the gap first — verify the domain, put a signup form on the site, set up bounce handling — then reply on the existing case. Opening a fresh request instead throws away the context the reviewer already has. Do I need a verified domain for SES production access? You are not formally required to have one, but a request from an account that has verified only a single email address gives the reviewer nothing to check, and it is the most common reason a request stalls. Verify the sending domain, enable DKIM and wait for the status to leave Pending, and publish SPF and DMARC records before you submit. Does this tool send my denial text anywhere? No. The matching runs in your browser with plain keyword rules, and the request text is assembled from fixed templates in the same place. There is no account, no upload, no model call, and no server involved. Deterministic templates are the point: this output goes to AWS support under your name, so the same answers always produce the same words. [Getting out of the sandbox](https://wraps.dev/blog/ses-sandbox-guide) The whole path, start to finish: what the sandbox restricts, what to have ready, and what a denial actually means. [Sending limits](https://wraps.dev/ses/limits) Sandbox quotas, the per-second rate against the rolling 24-hour cap, and how increases actually happen. [SES cost calculator](https://wraps.dev/tools/ses-calculator) What the volume you just quoted actually costs at AWS pricing, infrastructure included.