I'm currently working on my MVP for a job platform called Injobnito. Despite having no real user traffic, my last AWS bill was a hefty $415, which feels excessive at this stage. I'm considering downgrading my EC2 instance types and switching from io2 storage with provisioned IOPS to gp3 for my RDS. I currently maintain 5 EC2 instances for various functionalities: App, Chat, Backend, Admin, and Landing, along with ElastiCache and RDS. I'm looking for tips on how I can significantly lower my bill, ideally to around $100/month, while still keeping everything stable. I appreciate any experiences or suggestions you can share!
4 Answers
General advice for keeping AWS costs down is to always start with the smallest, cheapest options. Try to run services combined on fewer instances, and consider using Aurora Serverless for your database needs. You can always scale up your architecture once you start getting users.
Wise advice! Simple solutions often work better for MVPs, especially when you're early on.
Research cost management tools like AWS Cost Explorer to see where your expenses are coming from. You might find specific services or areas where you can make significant cuts.
Great tip! Seeing a detailed breakdown helps identify the money drains on your AWS bill.
Consider using serverless options like Lambda and DynamoDB instead of EC2 and RDS, especially since your user base is currently non-existent. This model can scale to zero, which could prevent you from having to pay for resources you're not using right now.
Right! Serverless is often a lifesaver for MVPs, especially when you're just starting out.
Absolutely agree with that! Going serverless could really help you save big bucks.
You might want to rethink why you have separate EC2 instances for every app. It's often better to use containers and consolidate everything into fewer instances. Also, if ElastiCache isn't providing caching benefits, consider ditching it since it might be unnecessary with low to no user activity.
You're definitely right! Why pay for multiple servers when one could do the job, especially during early stages? Containers can save you a ton!
For sure! Every instance you can cut down on equals savings. You could run several services on a single instance to keep costs low.
Yes! The key for MVPs is to keep things simple; otherwise, you risk unnecessary expenses.