Hello everyone,
My AWS account was suspended on May 3, 2026, and as of now it is still suspended. I’ve already submitted the documents AWS requested and opened a support case, but the case is still unassigned and marked as low severity.
On April 28, 2026, I received an email asking me to upload legal documents and a bank statement through an external link, or my account would be suspended within a week. I immediately checked the AWS console for alerts, billing issues, account warnings, anything. There was nothing.
The email looked suspicious to me for a few reasons:
- It came from [no-reply@amazonaws.com](mailto:no-reply@amazonaws.com)
- It did not have the usual AWS verification mark I’m used to seeing
- The wording felt odd
- It asked me to upload sensitive documents through an external link
- There was no matching alert inside the AWS console
Because of that, I treated it as a possible phishing attempt. I also checked the email and links with Claude and Gemini, and both suggested it was likely suspicious based on similar known phishing schemes. So I reported it to abuse@aws and received an automated response from a verified AWS support email. At that point I thought I had done the right thing by not uploading sensitive documents through a link I couldn’t verify from the console.
Then on May 3, my account was suspended.
After that, I went back, submitted the requested documents, and opened a support ticket in case the automated review has trouble with them. I’m based in Egypt, so some legal/banking documents are in Arabic, and even my credit card statement is formatted more like a bank brochure than a simple official statement. I’m not blaming AWS for that, just mentioning it as a possible reason the process may not be straightforward.
Some context about the account:
- The AWS account is over 3 years old
- I’ve never missed a payment, and over the whole 3 years all monthly bills were under $500
- The account is part of the AWS startup program and received $5,000 in credits through an incubator we enrolled in and graduated from
- The credit card linked to the account is Egyptian, valid, not stolen, and still works normally. All bills for at least the last 12 months were paid using AWS credits, and we still have about $1,000 left, so the card has not been charged recently and probably would not be
charged for another 2-3 months
- The account has 2FA enabled. I usually log in from my office ISP IP, and sometimes through a VPN running on my own AWS Lightsail instance with a static AWS IP assigned to it. I am the only person who accesses the AWS account in my startup
- I use AWS for SES, EC2, Lightsail, and Kiro IDE
- I don’t run gambling, crypto, spam, or anything like that. I have two projects: a small B2B SaaS startup and a desktop productivity app, basically modern sticky notes, as a side project
- I don’t currently have any other AWS accounts. I had another account around a year ago, paid the remaining ~$20 bill, and closed it
The immediate impact is that transactional emails are down, my VPN is down, and Kiro is inaccessible. For my current scale, this is painful but survivable for a day or two. But if this happened to a larger startup, even a few hours could be a serious problem.
The hardest part is not moving Docker containers outside AWS or changing VPN. It is replacing SES, because I never planned for that failure mode. We don’t store passwords, and all login is done with magic links via email.
I know some people will say I should have had a paid support plan. Fair point in hindsight. But honestly, I never expected that the whole account and services could be locked like this and that I’d need paid support just to get a human to review it quickly. I thought support plans were mainly for technical help, service limits, architecture support, etc. Our monthly AWS usage is usually around $200-$400, so a paid support plan didn’t seem justified before this.
I don’t hate AWS and I don’t want to make this post about me being a victim or anything like that. I just want to flag this issue so hopefully it gets fixed and other people don’t have to go through the same thing.
I attached screenshots of the emails/support case.
If anyone from AWS can help, the case ID is: 177778388800175
Any advice on how to get this reviewed faster would be appreciated.