It is no secret that it is not that hard to accidentally spend a boatload of money on AWS. This Twitter user told the story of his $77,000 mistake with a monkey emoji (because what’s funnier than spending the price of an entry level Tesla by accident.) The scary part is that many of us have been there. If you are not looking at your cloud bill every day, it is easy to let the costs run up quickly, then suffer from bill shock when it arrives a month later.

We’re often asked what are some of the top areas where we see customers overspending? Data transfer costs from misconfigured NAT Gateway definitely tops our list as one of the most common. In this article we’ll walk you through five steps to find which data transfers you’re overspending on and how to you can eliminate those excess charges.

Amazon recently announced the rollout of their new AWS Savings Plans, a new way to reduce your cloud compute costs. These allow you to achieve the discounts associated with their popular Reserved Instances (up to 72% off on-demand pricing) without having to engage in the headache of managing the same. With the new plans, you would commit to a particular hourly spend of your choosing on either a 1 year or 3 year fixed term.

Last week, Amazon announced the end of the reserved instance, commonly known as the “RI”, with the announcement of their new replacement, “AWS Savings Plans”.

If your business depends on AWS cloud services, you’re probably familiar with the experience of having unexpected, hidden charges crop up on your monthly invoice. At times, the AWS cost structure can be quite opaque, making it difficult to accurately gauge in advance the costs of hosting a given application. One of the most common sources of unanticipated AWS charges is the service’s data transfer fees.