Optimizing cloud spend for efficiency at scale

Understanding the ins and outs of cloud spend is a challenge for many, and when it’s time to scale, the budget hit can be a shock. According to a Gartner report, up to 70% of cloud costs are wasted, and a 2021 Arlington Research survey found that 82% of IT and cloud decision-makers have encountered unnecessary cloud costs — and 86% don’t feel they can get a comprehensive view of all their cloud spending.

A new client came to us recently to ask our help with adapting to a spike in use and its effect on their cloud spend. Their current platform was not designed to support heavy usage, so when traffic surpassed their expectations, they elected to migrate to a cloud platform better capable of handling heavier loads. Because of its extensive offerings and reputation for high uptime, they chose AWS.

Four best practices for cloud cost optimization

Our experience with cloud services has shown us time and time again that cloud budgets can take a serious beating if several key elements aren’t reined in. These include mismanaged or unattached resources, waste due to idle resources, inefficient monitoring of demand, and computing service inefficiencies. The four best practices we implement in cases like these are:

1. Identify unused or unattached resources — Often an administrator or developer might utilize a temporary server and later forget to shut it down when the job is over, or an administrator may neglect to remove storage attached to terminated instances. Check for open resources that can be shut off.
2. Consolidate idle resources — If an idle computing instance has a CPU utilization level 5% or less, the company might receive a bill for 100% of that computing instance — that’s a big waste of budget. To combat this, identify these instances and consolidate them.
3. Use heat maps to monitor and respond to demand spikes — A heat map identifies peaks and valleys in computing demand and uncovers opportunities for setting start and stop times to reduce costs. Take advantage of automation options to trigger starts and stops and conserve budget.
4. Right-size computing services — Analyze computing services and adjust them to the most efficient size, and also optimize for efficiencies in memory, database, computing, graphics, storage capacity, and throughput.

The Pegasus One approach

To help our client significantly reduce AWS cloud spend, we reviewed their infrastructure against our proven best practices and implemented the following changes:

1. Implemented strategic burstable performance instances
2. Audited outbound data transfers
3. Eliminated dependence on elastic IP addresses
4. Deleted EBS Snapshots

This post appeared first on Pegasus One blog. You can visit the full article here: Optimizing cloud spend for efficiency at scale — Pegasus One