I'm currently managing an RDS MySQL database which runs all day, every day, but since my application is only used during regular working hours (9 AM to 5 PM), I suspect I'm wasting a lot of resources (and money) keeping it live around the clock. I'm considering switching to Aurora Serverless to possibly lower my costs, but I'd like to get some opinions on whether this is a wise move, especially since my current Free Tier doesn't cover it and I would need to upgrade. I'm also open to alternative suggestions that could help reduce my RDS expenses. One idea I've had is to automatically shut down my database outside of the work hours, but I worry about needing access unexpectedly. What do you think?
5 Answers
I’d steer clear of Aurora Serverless if cost is your main concern. It might actually end up costing you more than a t3.micro instance. If you’re trying to save money at that level, consider moving to EC2 and managing backups with regular EBS snapshots instead.
If you’re really concerned about expenses and need MySQL, just automate the startup and shutdown of RDS. You can also have some logic in your app to handle downtime gracefully, which should cut your costs without too much hassle.
Keeping it straightforward is key. If your database use is minimal, staying with the traditional MySQL RDS setup is probably your best bet. You can easily set up a CloudWatch rule coupled with a Lambda function to turn your database off at night and start it again when you need it. This way, you won’t be paying for unused hours, but it won’t complicate things too much either.
If you're mostly operating from 9 to 5, just sticking with RDS and scheduling it to stop and start is the simplest and cheapest approach. It means you don’t have to go through the hassle of migrating databases. Plus, if you really need access in the wee hours, you can just turn it back on then.
That sounds smart! I like the idea of just starting it whenever needed and letting it rest the rest of the time.
Don't overlook the option of a t4g.micro; it can save you even more! Also, make sure you’re not accidentally using features like Multi-AZ or having unnecessary backups activated, which can drive up costs without you realizing it.
Absolutely, I agree! It’s all about maintaining simplicity while being cost-effective. I might go that route myself.