- Newest
- Most votes
- Most comments
I understand your frustration with the lack of response to your SES production access request. This situation is not uncommon, as processing times for SES Production Access requests can vary significantly. While some requests might be processed quickly (like port 25 restriction removals), others can take longer - sometimes several days or more.
While waiting for a response, here are some steps you can take:
-
Monitor both your support case and email inbox for any updates or requests for additional information.
-
Check if there are any "More information needed" notifications in your case that might require your response.
-
Follow up on your case through the AWS Support console. You could try using the chat option in AWS Support to inquire about the status of your request.
-
Ensure you've chosen an appropriate severity level for your case, as response times can vary based on the selected severity.
-
Update your existing ticket to clearly state the business impact this delay is causing and request an escalation.
-
If you have an AWS Account Manager or are working with an AWS Partner, reach out to them for assistance in escalating the issue internally.
The AWS SES team typically needs time to review the details provided in your request and determine next steps. They may be processing your request even if you haven't received a direct response yet. If the delay continues to be excessive, consider mentioning in your case update that this extended wait time is severely impacting your operations.
Sources
AWS SES | Production level request | No response even after 72H | AWS re:Post
How to get a hold of a human | AWS re:Post
Relevant content
- AWS OFFICIALUpdated a year ago
