I created an AWS account so I could learn the platform, using my normal email and payment details. I did not launch any services, create resources, or perform other actions. A few hours later, the console reported that authentication failed because the account had been suspended. The automated support information says there are no overdue or pending charges, so this does not appear to be a billing problem. I tried registering again with a second email address, but that account was suspended immediately as well. Has anyone dealt with this, and what is the best way to get the suspension reviewed when standard support has not replied?
2 Answers
Yes, automated risk systems can suspend accounts for reasons other than unpaid bills. They may flag registration details, payment or identity verification, links to other accounts, unusual signup patterns, or suspected abuse. Since there was no actual usage, the account probably needs a manual review rather than troubleshooting inside the console.
The practical route is to open or update a billing or account-support case through the official support portal, even if the account has no charges. Include the account ID, signup time, email used, and the exact suspension message, and ask for an account-integrity review. If a previous case exists, reference its case number so it can be routed to the team that handles suspended accounts.
A support representative can usually locate the case from its ID and redirect it internally if the first queue cannot resolve it. Avoid sending payment details or other sensitive information anywhere except the official support form.
The exact trigger usually is not disclosed, but creating several accounts can itself look suspicious. It is better to stop making new accounts and wait for the original case to be reviewed.