The promise of public cloud is the allure of decentralization and agility. But without proper methods to gain oversight and ensure optimization, chances are you may be succumbing to a variety of sins that are costing you time, money, efficiency, and governance.
We’ve recently posted our latest eBook, Avoiding the 7 Deadly Sins of Public Cloud Costs, looking at all the ways your public cloud costs can spiral to the depths but also best practices for pulling your enterprise back up.
This is the second in a weekly blog series examining each of the seven sins (the first was on zombie resources). This week we’ll look at Sin #2: keeping resources going even when you don’t mean it.
Sin #2: Keeping Resources on 24/7
Ever leave the lights on in your garage for the entire night without noticing them? Hate it when that happens! And just like electricity, public cloud uses a pay-what-you-consume model. Thus, if you spin up public cloud resources and don’t turn them off when not in use (such as weekends or weeknights) you’ll pay out the nose without even realizing it.
If you’re running a big team or have lots of applications, this can get out of hand quickly.
Pushing owners to turn off their resources when not in use is an easy solution. You can use reports and dashboards to understand your usage and spot the underutilized resources. It’ll help you save and maintain resource efficiency.
Cleanse Your Organization of Public Cloud Cost Sins
Looking to learn more about the six other deadly sins of public cloud costs? Download the eBook today. Also be sure to check out our comprehensive AWS Cost Optimization Guide for best practices on AWS costs.