How can I reach a human about a suspended AWS account?
Asked by
MellowPine42
My AWS account was suspended for a non-billing issue, and my application has been offline for about two weeks. Because I can't access the database, my users are unable to sign in or use their accounts. I last heard from a human support representative roughly a week and a half ago, and my attempts to request a callback or use chat haven't led to any useful updates. I've been a customer for more than three years and urgently need to know how to reach someone who can explain the suspension or help resolve it. I'm based in Europe, if regional support options make a difference. I suspect the suspension may be related to an alerting bot we configured, but I haven't received confirmation.
Answers
If you receive another response, ask directly whether the issue is an automated security or abuse flag and what verification or remediation steps are required. A regional AWS account team or sales contact may be able to route the escalation, but avoid opening unrelated duplicate cases because that can make ownership less clear.
Reply to this answer
Account suspensions are usually handled by a specialized account or trust team, and regular technical support may not be able to disclose much. Keep the existing case active, provide the case number and business impact clearly, and explain that production users are locked out. Also review recent security, abuse, and automated-alert activity in case something triggered the suspension.
Reply to this answer
If you’ve previously worked with anyone in AWS sales, account management, or the solutions architecture team, try contacting that person through your existing business channel. They may be able to identify the right internal team or escalate the case. If you have a paid support plan, make sure the case is categorized under account access or account support rather than a technical service issue.
MellowPine42: I’ve already tried the normal support routes and haven’t received a useful update, so I’m mainly looking for any legitimate escalation path that can get this reviewed quickly.
Reply to this answer
Add your answer
Answers are reviewed before publication.
MellowPine42: The only likely trigger I can think of is an alert bot we configured, but I haven’t been told whether that caused the suspension.