Every contact with AWS about SES access goes here, verbatim, with the date, the case ID and who replied. The earlier attempts were not logged properly, so the reasons for the denials are guesses.
How to use it: when you submit, paste the exact text and the case ID. When AWS replies, paste the exact reply before you answer it. When you answer,
paste what you sent. Never edit an entry afterwards; add a new one. This log is for contact with AWS only; decisions and status live in
README.md and gap-log.md.
What is known about the earlier attempts
Reconstructed from the repo and notes on 2026-10-05. The AWS wording and case IDs are missing. Add them if you still have them (SES console → Support Center → Your support cases, including resolved ones).
| # | Submitted | Outcome | Notes |
|---|---|---|---|
| 1 | 2026-07 (the old draft says 07-04) | Denied 2026-07-11, "for security reasons we are unable to provide specific details" | Declared Transactional; the narrative mixed in newsletters. Multi-tenant platform pitch. Case ID: ______ |
| 2 | 2026-07 (the old draft says 07-16) | Denied 2026-07-19, same wording | A more detailed resubmission. Case ID: ______ |
| 3 | Drafted 2026-07-25, never submitted | Judged unsafe on 2026-07-28 | Several claims were untrue (listed in ../aws-ses-production-access-case.md). |
The submission dates in the old draft (07-04 and 07-16) and the denial dates (07-11 and 07-19) do not obviously line up; the console is the source of truth. Other documents say "denied on" 2026-07-11 and 2026-07-19.
Entries
None yet. Nothing has been submitted to AWS since the denial of 2026-07-19.
Template for new entries
### YYYY-MM-DD — <submitted | AWS replied | we replied | escalated | approved | denied>
Case ID:
Channel: <production-access form | Support case | chat | phone>
Who:
Verbatim text:
> ...
What I did next:
Evidence filed: