A $1k AWS bill led me to redesign my ECS architecture
1 point · 0 comments
I’ve been building on AWS for over a decade. I know how the pricing works. I’ve designed cost-conscious architectures for companies that process millions of requests. I still managed to rack up a $1,000 AWS bill on a side project.
The project is Lush Aural Treats , a music-focused API service running on ECS Fargate. Nothing exotic. Standard containerised workload, standard AWS architecture. The kind of setup you’d find in any “deploy to ECS” tutorial.
I accidentally spent ~$1,000 running a small ECS project on AWS.
Baseline infrastructure cost dropped from ~$50/month to near zero.
The next step would be replacing Fargate with Lambda for event-driven workloads. Haven’t done that yet, but it’s on the list.
When I deployed Lush Aural Treats, I reached for the usual AWS primitives: