AWS SES sending paused and no response after detailed descriptions of changes was shared (Going on two weeks of crickets).

When AWS SES pauses your account's ability to send emails due to high bounce rates, it can be frustrating to wait for a response, especially when you've already addressed the issues. Here's what you can do in this situation:

1. Review your AWS Support plan level. Response times vary significantly based on your support plan. Basic support plans typically have longer wait times and limited access to technical support.

2. Check the AWS Support Center for the case that AWS opened regarding this issue. Make sure you're responding directly to that case rather than creating new ones, as this helps maintain continuity in your communication.

3. If you haven't received a response after two weeks despite following up, consider:

• Opening a new support case specifically about the lack of response
• Upgrading your support plan temporarily for faster response times if this is critically impacting your business
• Checking if the notification email came from a specific address that requires a direct reply

4. While waiting, ensure you've documented all corrective actions taken:

• How you've cleaned your email list
• Implementation of suppression lists
• Changes to prevent future high bounce rates
• Metrics showing improvement since the changes

Unfortunately, extended wait times can occur, especially with basic support plans. The SES team needs to review your case thoroughly to ensure the issues have been properly addressed before restoring sending privileges.

For future reference, maintaining clean mailing lists, implementing proper opt-in procedures, and regularly monitoring your sending health metrics can help prevent these situations.
Sources
AWS SES Sending Paused and No response from AWS Team | AWS re:Post
SES send suspended without notification | AWS re:Post
Seeking Urgent Assistance: SES Account Paused Due to High Complaint Rate, Need Clarification and Resolution Timelines | AWS re:Post