Account suspended for two weeks—how can I reach a real support person?

Make the outage impact very explicit in the case: the application has been unavailable for two weeks, users cannot sign in because the database is inaccessible, and you need confirmation of the reason for suspension plus the exact remediation steps. Include timestamps, account identifiers, and any relevant security details, but don’t share sensitive credentials. If there is an account or billing contact on file, have that person follow up through the official support channel as well.

Account suspensions can sometimes be triggered by automated security or abuse systems, including monitoring or alerting setups that generate unusual activity. Review recent account notifications and security emails carefully, then provide a concise explanation of the suspected alerting bot, what it did, and what you changed to prevent a recurrence. Keep checking the original case rather than opening many unrelated requests, since duplicate cases can make escalation harder.

If you’ve previously worked with anyone in AWS sales, account management, or the solutions architecture team, contact that person directly and include the existing case number. They may be able to escalate it internally. If you have a paid support plan, make sure the case is categorized correctly; sometimes opening or updating it under the account-access category gets it routed to the right team. You could also look for an AWS representative in your region through professional networks, but keep the communication focused on the case number and business impact.