Independent AWS criticism

AWS sucks.
Here's why.

Bills that explode overnight. IAM policies nobody can reason about. Support loops, outage fog, egress traps, and suspensions that take your business down and then email you about it.

The record

Everything, newest first.

Marked Verified means it was written up here with the evidence attached. The rest are public submissions, posted unedited by the people they happened to.

Account suspension2026-08-05

AWS is simply a dumb pipe

I have learned that AWS cannot be trusted with persistent data. They can be used for compute resources for spot jobs, assuming you can get them to approve your limits (quotas..lol)…

anonymous

Account suspension2026-08-05

AWS is holding my data hostage with no explanation

I did nothing wrong. They still haven't told me what they think I've done wrong, but they have my data locked up in an s3 bucket that I cannot access. It's been 22 hours now, still…

anonymous

Account suspension2026-08-04

They suspended my account, took my email server down with it, then told me to read the email they sent me

AWS suspended the account running my mail server. The suspension notice was delivered by email. To the mailbox they had just switched off. 202 domains went dark.

Verified anonymous

All 3 →

Randos welcome

Post the story. Bring receipts if you have them.

No account. No signup. No email required. Write it, post it, it goes live. Firsthand accounts are best. Redact anything that could hurt someone who did not ask to be part of the story.

Gooddates, regions, service names, bill deltas, ticket timelines, public status links.
Redactaccess keys, account IDs, private customer data, internal hostnames, personal info.
Removedspam, doxxing, threats, and anything presented as fact that plainly isn't.

Text goes live immediately. Images are checked first — one screenshot can carry an account id, a customer list, or a live key, and a takedown an hour later does not un-publish any of those.

What gets published

Claims need receipts. Anger gets edited into evidence.

Anger is fine — it is usually the honest reaction. Sloppiness is not. One wrong technical detail is all anyone needs to dismiss an entire story, so the standard here is simple: say what you measured, say what you were told, and keep the two apart.

Screenshots

Images are checked before they publish. Text isn't.

A paragraph can be wrong and then corrected. A screenshot can carry a live access key, a twelve-digit account id, a customer list, or a face — and once it is published it is scraped, mirrored and archived within minutes, so taking it down an hour later takes nothing down. That asymmetry is the whole reason images wait and text does not.

Before an image is uploaded, the black boxes you draw on it are burned into the pixels in your own browser — the original never leaves your device. The server then rebuilds the image from scratch, which destroys the location data, device serial and the hidden thumbnail that phone editors leave behind holding the uncropped picture. Then a person looks at it. Then it goes up.

Getting something removed

If a story exposes you, say so and it comes down.

Stories publish immediately, which means the wrong thing can go up before anyone reads it. If a post contains your personal information, someone else's private data, or a claim about you that is false, send it here with the link and what is wrong with it. Personal data comes down on sight, no argument required. Everything else gets read and answered.

A form, not a ticket queue, and no support tier gating it. Nothing to sign up for, nothing to verify, no case number.