AWS Charged Me $1,400 for a Mistake I Didn't Know I Made

I opened my AWS billing dashboard expecting maybe $40.

It said $1,400.

I stared at it. Refreshed the page. Thought it was a glitch.

It wasn't.

Somewhere, a service I forgot to shut down had been running for weeks. A test instance I spun up "just to try something" — and never turned off.

I didn't even know it existed anymore.

That's the part nobody warns you about when you're a non-technical founder using cloud infrastructure.

It's not just hard to use. It's silently expensive if you don't know exactly what's running, why, and what it costs.

You can't see the meter ticking. You just see the bill — after the damage is done.

I spent that night digging through dashboards I didn't understand, trying to find what to kill before it cost me more.

No alerts. No warning. No plain-English explanation of "hey, this is costing you $4/day and you forgot about it."

Just a number that ruined my week.

This is exactly the blind spot I built Ohuriya.com to close.

You ask: "what's running on my server right now and what's it costing me?"

Plain English answer. No dashboards to decode. No surprise bills.

You see what's running. You decide what stays. You're never guessing.

If you've ever opened a cloud bill and felt your stomach drop — you're not alone, and it doesn't have to keep happening.

#FounderLife #IndieHackers #BuildInPublic #StartupLessons #NonTechnicalFounder #CloudComputing #VPS #SoloFounder #OhuriyaAI #MicroSaaS