SES production access request: No response on case after 3 days, all requested info already provided

I understand you're waiting for a response on your SES production access request. While I can't directly intervene in your specific case, I can provide some guidance on what to expect and how to proceed.

Amazon SES production access requests are reviewed by AWS's Trust and Safety team to ensure compliance with email sending best practices and AWS policies. Review times can vary depending on the complexity of the request and current queue volumes. While many requests are processed within 24-48 hours, some may take longer, especially if additional information or clarification is needed.

Since you've already provided all requested information in your case correspondence, the best course of action is to continue monitoring your case through the AWS Support Center at https://console.aws.amazon.com/support/. If you need to add any additional context or follow up, you can do so by adding correspondence directly to your existing case through the Support Center.

The setup you've described—with proper domain verification, DKIM, SPF, DMARC, and bounce/complaint handling—demonstrates good email sending practices, which is exactly what the review process looks for. Continue to ensure all your responses in the case are complete and address any questions the team may have raised.

For the most direct path to resolution, stay engaged with your case through the AWS Support Center, where the team handling your request can provide updates specific to your situation.

Hi Pratham,

The frustrating reality here is that re:Post is a community forum — nobody here (including AWS employees who answer) can look up, route, or escalate an individual support case. So "monitor the case" isn't going to unblock you. Here's what actually moves the needle.

First, reset expectations on the timeline. SES production access is targeted at ~24 hours, but that's a target, not an SLA, and it slips when the Trust & Safety queue is backed up or when anything in the request needs a second look. 3 days with no reply usually means it's still queued, not that it's been missed — but there are concrete things you can do.

1. Reply on the case again to bump it

Each new correspondence re-timestamps the case in the queue. A short, factual follow-up ("Following up — all requested details provided on [date], happy to add anything else") is enough. Don't open a new case for the same request — duplicates get merged/closed and can push you further back.

2. Confirm your support plan includes case responses

This is the most common hidden blocker: on Basic (free) support, service-limit / production-access requests are handled but you have no response-time commitment and no ability to escalate. If you're on Basic, the fastest fix is often Developer support (or higher) temporarily — it gives you a response-time expectation and the ability to raise severity. You can drop back down afterward.

3. Use the right request path

For newer accounts the SES production-access flow lives under SES Console → Account dashboard → "Request production access" (which routes to the Trust & Safety review), rather than a generic "Service limit increase" case. If you filed it as a generic limit-increase case, that can route differently. Worth confirming the request type.

4. Strengthen the request content while you wait

Trust & Safety approves faster when the case removes all doubt. From what you described you're most of the way there, but make sure the case explicitly states:

• Exactly how recipients opt in (double opt-in? where is consent captured?) — the single biggest factor for the marketing portion.
• How recipients unsubscribe (one-click / list-unsubscribe header).
• Sample content / message types and sending frequency.
• Concrete volume numbers (emails/day) rather than "low" — vague volume invites a follow-up question, which restarts the clock.
• Your bounce/complaint process (you mentioned it — name the mechanism, e.g. SNS notifications + suppression list).

The marketing use case gets more scrutiny than pure transactional, so the opt-in / unsubscribe evidence is what typically makes or breaks the turnaround.

5. If you have Business/Enterprise support

You can raise the case severity and, for Enterprise, engage your TAM to follow up internally — that's the only legitimate "routing" path, and it's account-side, not via the forum.

One more note: you did the right thing removing the case ID from the post (Ben flagged it) — case IDs shouldn't be shared publicly.

Net: bump the case with a fresh reply, confirm you're not on Basic support (upgrade to Developer if you need a response commitment), verify you used the SES "Request production access" flow, and tighten the opt-in / volume details. That combination is what gets a stalled SES request moving.