AWS Has 200+ Services. You Probably Use 8.
And yet it still feels overwhelming. Here's why.
I had a cloud computing class at 19. I was the only one in the room who got it immediately. Not because I was smarter, but because the concept is actually simple.
I explained it to my friend like this: "You know how iCloud stores your photos somewhere and you can access them from anywhere? AWS does that for everything, not just photos, but apps, databases, entire companies." He got it in 30 seconds.
The cloud isn't complex. The interface is.
The 8 services problem
Most teams live in 5-8 AWS services. EC2, S3, RDS, Lambda, VPC. Maybe CloudWatch. Maybe ECS. The rest you Google when you need it.
But the console doesn't know what you use. It shows you everything. All 200+ services. Every region. Every tab. All the time.
So a simple question like "what's running in my account?" becomes 20 clicks, 3 region switches, and 6 browser tabs. The answer is probably 8 services. The journey to get there isn't simple.
The interface is the problem
AWS was designed in 2006 when there were a handful of services. The console grew alongside the product: new page for each service, new tab for each region, new click path for each setting. It works. It just doesn't scale to how you actually think.
You think in questions. "What's expensive?" "What's broken?" "What changed today?" The console doesn't answer questions. It shows you data and asks you to figure it out.
When you just ask "what's running?" in plain English and get a clear answer in 3 seconds, you realize the cloud was never the problem. You were using the wrong interface.
The stuff underneath is genuinely cool. Everything runs on cloud. Netflix, Canva, your bank. All of it. One small issue in a datacenter and boom, it's down. True stories.
Cloud is simple. The tools built on top weren't. That's what we're fixing.
— Founder, LiberraAI