Can someone please assist with [Case 175030033900120] this is for Amazon SES I responded and have not had a response back.

I understand your frustration with waiting for a response regarding your Amazon SES production access request. This situation is not uncommon, and several users have reported similar experiences with delays in processing SES production access requests.

Here's what you should know:

1. Processing times for SES Production Access requests can vary significantly, sometimes taking several days or longer, even though the expected turnaround time might be shorter.

2. The AWS SES team needs time to review your details and determine next steps. They may be processing your request even if you haven't received a direct response yet.

3. While waiting, keep monitoring both your support case and email inbox for any updates or requests for additional information.

If it's been more than a week without any response, here are some actions you can take:

1. Follow up on your existing case through AWS Support, possibly using the chat option to inquire about the status.

2. Ensure you've provided comprehensive information about your use case, including:

• The specific types of emails you plan to send (transactional, etc.)
• Your estimated email volume
• How you'll handle bounces and complaints
• Your methods for ensuring compliance with email best practices

3. If you're a new AWS customer, be aware that AWS often requires users to build trust by using the sandbox environment for a while before granting production access.

4. Implement proper email authentication (SPF, DKIM, DMARC) if you haven't already, as this demonstrates your commitment to following email best practices.

While you wait for production access, you can continue using the sandbox environment with its limitations to build a positive sending history that demonstrates responsible use of the service.
Sources
SES: Production Access | AWS re:Post
Production Access to Amazon SES Denied - what to do? | AWS re:Post
My SES status stuck at More information needed - case ID nnnn | AWS re:Post

i still don't get problem solved.