Has this happened to anyone else?

Search AWS complaints by service name, notice wording, case type, charge, outage, policy, or the thing support called it. The useful match is often not the company name; it is the exact phrase in the email or dashboard.

Billing shockThe bill is the most common reason people end up here, and it is almost never the compute. It is the NAT gateway processing charge on traffic you thought was internal, the cross-AZ transfer inside your own cluster, the e…

Outage or reliabilityThe failure is bad. The information is worse. The status page stays green while your pager does not, the update says "elevated error rates" for the third hour running, and us-east-1 takes services with it that you were t…

Support failureBasic support means you cannot open a technical ticket at all. Developer means one person, business hours, best effort. Business is a percentage of your bill for the right to be asked for a correlation ID you already sen…

Searchable evidence

The strongest matches on AWS Sucks come from the words that appeared in the bill, warning, appeal, support case, policy notice, dashboard, receipt, refund email, or outage update. A useful search can be a AWS detail, an error phrase, a line item, a product name, a region, a case type, or the exact wording a support script kept sending back.

The account ID, and the date and time the charge or suspension appeared.
The billing console line item: the service, the meter, the region.
The support case number, even if nobody ever replied to it.
What you had deployed that you believed was free or idle.

Common threads here include Billing shock, Outage or reliability, Support failure, Account suspension. Searching one concrete phrase usually beats searching only the brand name, because the long-tail wording is how two strangers find out they were handed the same problem.