- Newest
- Most votes
- Most comments
I understand your frustration with the SES production access request process and the lack of timely responses.
Based on the information provided, there are a few important points to clarify:
-
Response times for SES production access requests can vary significantly. While AWS typically aims to respond within 24-48 hours, many users have reported waiting several days or longer. Some users have reported waiting up to 8 days without updates.
-
Regarding your specific situation with the security concern related to an old case: When AWS denies SES production access, they often don't provide detailed explanations due to security policies. The reference to your previous security case (about the exposed API key) appears to be affecting your current request, even though you believe that issue was resolved.
-
For account-level issues like yours, AWS does provide basic support through email, but technical support cases require a paid support plan (Developer tier or higher). Basic support does not include technical support case handling.
-
Since your case involves both account access and a technical component (SES production access), you may be experiencing delays as the system determines how to route your request.
Some suggestions for your situation:
-
Be persistent but patient with your current case. Continue to monitor both your support case and email for any updates.
-
In your case updates, clearly explain that the previous security issue was resolved and the case was permanently closed. Provide specific details about what actions you took to resolve it.
-
If you need faster resolution, you might need to consider temporarily upgrading to a paid support plan to get technical assistance, though this is understandably frustrating when you're already facing delays.
-
Make sure your use case for SES is clearly explained, including how you'll handle bounces and complaints, your email authentication methods, and your compliance with email best practices.
Unfortunately, I cannot directly access or expedite your specific case, but these steps may help you move forward with your SES production access request.
Sources
Support not responding | AWS re:Post
SES Production request denied | AWS re:Post
AWS SES | Production level request | No response even after 72H | AWS re:Post
Unable to delete KMS CMK nor to open a support case | AWS re:Post
AWS Sales Support and Customer Sales Representative Contact Info - Amazon Web Services
Relevant content
- asked 2 years ago
- asked a month ago
- AWS OFFICIALUpdated 2 years ago