My Most Expensive AWS Mistake

I’m a firm believer in learning from others’ mistakes. So to help you out, I’d like to share how I accidentally spent $327.36 in AWS (thank the lord for AWS credits, which saved me). I was looking into migrating database instances from one engine to another recently, so I found a <a href="https://docs.aws.amazon.com/dms/latest/sbs/dms-sbs-welcome.html" rel="noopener ugc nofollow" target="_blank">tutorial from AWS</a> on how to do it. Innocently enough, I followed along with it but ran into some errors along the way (tutorials are rarely perfect because of the rate the underlying technology changes). I did some troubleshooting for a couple of days, but naturally, I got distracted and put it down for a couple more days. I eventually received a budgets alert one day that my spending had surpassed my budgeted amount, but unfortunately, budgets alone will not remediate all issues regarding runaway spending. So about a week later, I took a look at my cost explorer and was shocked to find that I had amassed $327.36 in RDS charges! It took me a second to figure out why, but then it dawned on me, and I was quickly able to remediate it by terminating my DB instances. According to RDS pricing, you pay for the storage you provision, even if you are not actively using it. Additionally, you pay for DB instance hours, with the price being based on the DB instance type you are consuming. <a href="https://aws.plainenglish.io/my-most-expensive-aws-mistake-831b5fd59d3c">Visit Now</a>