Amazon Web Services (AWS), is a great place for unlimited storage and compute to meet your enterprise IT needs. It allows you to scale IT resources up or down without needing to make large capital investments upfront. This can help speed up your time to market or give you a rough idea of the IT cost and feasibility of new IT projects.
This is a double-edged sword.
If not controlled and monitored, the ease of AWS usage and its cost-per hour billing can lead to high costs. It can be compared to a personal credit card that you can use when you have no cash. This is dangerous on many levels.
Your AWS resources running 24/7 is like a high interest rate credit card. You build more debt until your balance is paid. It is possible that you set up the large EC2 server with the intention of turning it off when it was finished. What about the rest of your team? Are they disciplined enough? Are they able to pay off their credit cards each month to zero?
If you don’t close down your AWS EC2 instances you will be billed every month even if they aren’t being used. AWS will bill you if you run it. AWS will not automatically inform you that your machine is running without any benefit. Why would it? You’ll be billed for redundancy if you copy your data across multiple AWS areas.
AWS can have hidden fees that you don’t know about until you receive your bill. This is just like with credit card issuers. For instance, data download costs. It’s easy to get data uploaded — it’s unlimited, free! The downside is that the more data you upload, the higher the storage costs. You will also have to pay for data storage if you need it for someone else (or a colleague outside your organization).
Glacier, AWS’ bulk storage option, is it worth considering? Cheaper, right? Yes, it is cheaper, but you will need to “rehydrate” your data back to AWS Simple Storage Services (S3). You will then be charged twice for downloading it.
AWS allows accounts to download a certain number of data per month for free, but this won’t work well for larger data sizes. There are cheaper tiers available for larger downloads. If you need large data files, there are two options: either rip off the Band-Aid and pay the full monthly charge or slow down the download. Most people will choose something in the middle.
AWS can charge for additional services. These costs may not be significant, but they should be considered. My team and I have started to investigate our use of AWS services. Although we are still early in the process, here are some helpful tips:
You shouldn’t be looking at your AWS costs every single day, just as you wouldn’t check your weight on the scale. It can become an obsession, and you may lose sight of the bigger picture. It is best to look at it weekly or biweekly depending on how large your AWS resources are and what your budget with AWS.
AWS provides tools to view billing information in its interface. This is a good place for you to start. AWS offers a free tool that allows you to analyze your costs. AWS will then produce a report with cost-saving recommendations. It can provide some insight and help you start conversations with your team members and end users.
As you become more familiar with how things are charged and the billing process, you can start to look at your billing over time. We downloaded the details from AWS in text files, opened it in Excel, and then we billed.
0