I recently found myself in a tough situation where AWS suspended my account, and now my production environment is down. I had been dealing with verification issues for several days. I submitted all requested documentation, including my passport and business formation papers, multiple times as AWS escalated the issue through their support channels. Despite my efforts and communications with various support representatives, my account was suspended with no clear reason given. I've even been informed that my account is supposedly related to previously closed accounts, which is completely false as we only created this account four months ago and have no connections to any other accounts. My entire infrastructure is at risk of deletion if this isn't resolved soon. Has anyone else gone through a full suspension at this level of compliance and managed to recover?
4 Answers
Sorry to hear about your troubles. It used to be that AWS did everything to keep a customer happy. I don’t get what's happening now either. They need to resolve these issues before it's too late for businesses like yours.
I went through a similar situation last month, but thankfully my account was reinstated after a couple of days. It took a lot of escalation and persistence on my part though. They initially suspended my account after flagging requests from a different region, which seemed unfair since that's a normal practice. But keep pushing — you're not alone in this!
That's strange! I've been making cross-region requests too, and my account is fine. Sounds like there's more going on here!
It's wild that they can flag legitimate traffic while overlooking actual phishing sites doing way worse things.
I just saw your update and it's totally unacceptable. If they're claiming connections to closed accounts without evidence, it raises a lot of red flags. This isn't just about verification anymore; it's damaging your business's credibility. Keep insisting on clarity and document everything!
What frustrates me is how they’ve changed their stance so suddenly. There’s gotta be someone high up who can push this through for you.
And seriously, backup your data and DNS especially if everything is in AWS. Don't let this happen again!
This is a scary reminder of relying heavily on AWS for everything. I've always been careful to have backups but seeing your situation makes me realize I need to be even more cautious. Good luck getting this sorted out!
Right? You can do all the best security practices, but at the end of the day, AWS's actions can bring everything crashing down.
Frugality seems to have overtaken their customer-first approach. It's frustrating to see.