Resources Webinars

Cloud cost optimization: strategies to avoid overspending

Cloud spend is easy to start and hard to account for, and by the time it is a line item somebody is defending, the causes are spread across a year of decisions. Frank Gill works through the practical ways to bring it down without trading away the performance the spend was meant to buy.

Free to watch. No registration.

What the session covers

  • Right-sizing against real usage. Assessing what a workload actually consumes and aligning the provisioned resource with it, which is where most of the recoverable spend is.
  • Workload placement. Distributing work so performance improves and cost falls together, rather than treating the two as a trade.
  • Continuous monitoring. Finding cost leaks in real time, with the tools and methods for catching one before it appears on an invoice.
  • Balancing cost against performance in practice. The methods that hold both, and how to tell which of the two a given change is actually buying.
  • Keeping a budget lean once it is. What it takes for the saving to survive the next six months of changes.

Who it is for

IT leaders

Answering for a cloud bill that is rising faster than the workload behind it.

Cloud architects

Deciding how workloads are sized and placed, which is where most of the cost is set.

Business strategists

Weighing what the cloud investment is returning and what a lower bill would cost in capability.

After the session

Finding the spend in your own estate

Every technique in this session depends on knowing what each workload consumes and what it is for. That is the measurement most estates do not have, which is why the bill is hard to argue with.

A cloud assessment produces it. The savings then follow from the data rather than from a general principle about right-sizing.

Know which workloads are driving the bill

Most cloud overspend is not one large mistake. It is a long tail of resources sized for a peak that never came, and finding it is a measurement exercise before it is an engineering one.

Let us show you what's possible.

Two ways to start