There are other costs associated with moving out of RDS. You may spend less on your hosting/storage but you will likely be spending more time on maintenance. Yo

There are other costs associated with moving out of RDS. You may spend less on your hosting/storage but you will likely be spending more time on maintenance. You'll now be in charge of executing snapshots and making sure they work. If you have someone on hand that has the time and is willing to be on call for managing the DB that's great and it's probably worth it. But if you have to hire someone or have to move someone of of other work to take care of the DB it may not be worth it. And if you can't hire someone and don't have someone with experience in managing a prod DB it could be a risky move. Speaking of moving, the move itself can be risky. It can be tricky to move data like this depending on whether or not you can take some downtime, how much downtime, what your data access patterns are, if you can easily dual write and how long it will take to transfer the data are some things to think about. The cost of the move itself in dev time and testing costs (you will probably want to make sure this works before doing it for real, which means starting up copies of your DB in both AWS and your new provider) might blow away any savings you might make for some time. It also depends on the DB tech you are using. Some are more reliable than others and require very little attention. I don't know enough about your situation to give you definite advice but those are the things I would consider before moving. There are a lot of non-direct costs associated with something like this so it's best to think through everything. Some other things to consider are dev familiarity (they used one tool now they need to learn another), monitoring and observalbility (you didn't mention using cloudwatch but it's there), security and upgrades/updates. Good luck with whatever you decide on.