I created an AWS account to learn the platform, using my usual email and payment details. I didn't launch any services, create resources, or perform any other actions, but several hours later I could no longer access the console because it reported that the account had been suspended. The support assistant indicated that there were no overdue or current charges, so this doesn't appear to be a billing issue. I also tried registering with a second email address, but that account was suspended immediately as well. What could trigger this, and how can I get the account reviewed when support hasn't replied?
3 Answers
Opening another account with a different email is unlikely to help and may make the automated checks more suspicious. Use the original account’s support channel and provide the account identifier, registration details, and the suspension message. Ask specifically for an account or trust-and-safety review, then wait for that team’s response rather than repeatedly creating new accounts.
This can happen to legitimate new customers, including business accounts, because registration screening is automated. A billing chatbot saying there are no outstanding charges doesn’t rule out an identity, payment-method, or account-association review. The practical solution is to keep the support case open and request escalation to the team that handles suspended accounts.
Yes, automated AWS risk systems can suspend accounts even before resources are created. Possible triggers include identity or payment verification problems, links to previously restricted accounts, unusual registration patterns, or other signals in the automated fraud checks. The exact reason usually isn’t disclosed publicly, so only AWS Support can review and reverse it.
That makes sense, but I’m mainly wondering what kinds of non-obvious issues can cause it when there was no usage or intentional policy violation.