No items found.
Cloud & AI Cost Management
On-demand Webinar
On-demand Webinar

Is it time to shift cloud cost ownership left? | Harness Resource

When it comes to your cloud spend, how confident are you that every dollar is doing real work? Could you put a number on what percentage goes on the idle, overprovisioned, or forgotten resources quietly draining your budget?

Your developers could be the untapped resource you need to track – and reduce – cloud spend. With a deep understanding of internal systems, they’re uniquely placed to build cost awareness into architecture and workflow decisions – yet in most organizations they’re shielded from the bill. With 62% of developers asking for more responsibility over cloud spend, the challenge for engineering managers is providing the culture, guardrails, and tooling that empower developers to reign in mounting costs.

In this webinar, our panel discusses what it takes to shift cloud cost ownership left: the strategies for baking cost visibility into workflows, where savings can be automated, and how to foster tighter partnerships between engineering and finance to optimize cloud spending without sacrificing on delivery.

Key takeaways:

  • How to build cost-aware habits into everyday engineering work
  • Leveraging visibility and automation to empower developers to cut cloud costs
  • Breaking down the silos between finance and engineering for greater cost awareness

Published
January 1, 2024

Guide on its way

Check your inbox — your playbook is ready.

You're all set

Check your inbox — your download is on the way.

Redirect link
Redirect link

What you'll learn

Key Takeaways

Cloud spend can signal business growth

High cloud costs are acceptable if they are understood and support business objectives. Investigating usage spikes allows companies to confidently invest and grow faster.

Foster a blame-free experimentation culture

Encourage engineers to take ownership of cloud costs without fear of punishment. If an experiment causes an issue, it indicates a need for better processes rather than individual fault.

Frame architectural shifts in business terms

To justify upfront technical investments like migrating to ARM, engineers must speak the language of business stakeholders. Proposals should highlight how architectural changes impact product scalability and overall offerings.

Do not accept unexplainable cloud costs

Cloud expenses must always be contextualized, as large sums might simply represent business as usual. Teams should investigate unlabelled or mysterious costs to ensure resources are used efficiently.

Utilize disposable development environments

The cost ratio between development and production environments varies widely based on data needs and traffic. Leveraging the cloud's ability to quickly spin down and dispose of resources is crucial for optimizing development costs.