I received an automated warning from AWS stating that my business's account would be suspended unless I addressed some suspicious activity they detected. I checked my account, deemed the flagged activity a false alarm, and responded to their inquiry, thinking this would resolve the issue. Unfortunately, my account was still suspended. It's been several days, and I'm still waiting for an agent to review my case. I can't access the console, and my team has crucial sales calls lined up this week that rely on the data in that account. Is this a regular issue for others who've faced similar flags? How long should I realistically expect to wait for a response? I feel quite helpless due to this mistake, and it could seriously affect my business.
EDIT: I've discovered there's an AWS support account — could they look into case **175813869600548** and possibly escalate it?
4 Answers
AWS accounts should have more default protections to prevent these situations. It can be a bit of a mess otherwise.
Exactly! New accounts start in a limited Free Tier, which makes it hard to get into serious trouble right away.
I understand your frustration. Unfortunately, we can't disclose account details or case specifics in this forum, but I have relayed your concerns to the team. Please keep an eye on your support case for updates.
If AWS flags your account, it's usually due to something genuine. It happened to us a while back when we found mining software on our EC2 instance. We terminated it, tightened our access controls, and informed AWS about the action we took. Setting up GuardDuty also helped prevent future issues.
What was the reason for the false alarm? Knowing the specifics might help others understand what to do in this situation.
That's true! The quota system is meant to mitigate these issues, although many users still have complaints about it.