<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Cloud Cost Optimisation on Darshan Deshmukh</title><link>https://darshandeshmukh11.github.io/tags/cloud-cost-optimisation/</link><description>Recent content in Cloud Cost Optimisation on Darshan Deshmukh</description><generator>Hugo</generator><language>en</language><lastBuildDate>Tue, 04 Aug 2026 01:22:40 +0900</lastBuildDate><atom:link href="https://darshandeshmukh11.github.io/tags/cloud-cost-optimisation/index.xml" rel="self" type="application/rss+xml"/><item><title>From Cloud Waste to Cloud Discipline</title><link>https://darshandeshmukh11.github.io/projects/cloud-governance-finops/</link><pubDate>Tue, 04 Aug 2026 01:22:40 +0900</pubDate><guid>https://darshandeshmukh11.github.io/projects/cloud-governance-finops/</guid><description>&lt;h1 id="cloud-waste-doesn">&lt;strong>Cloud Waste Doesn&amp;rsquo;t Happen Overnight&lt;/strong>&lt;/h1>
&lt;p>&lt;strong>How I stopped treating cloud governance as an audit and started treating it as an engineering workflow.&lt;/strong>&lt;/p>
&lt;p>During my early years working with AWS environments, I assumed cloud governance was something teams reviewed every few months. A security assessment, cost optimization exercise OR a compliance report before an audit.&lt;/p>
&lt;p>The process always looked similar. Run a few scripts —&amp;gt; Export a spreadsheet —&amp;gt; Raise a list of findings —&amp;gt; Assign them to different teams —&amp;gt; Wait for them to be fixed.&lt;/p></description></item></channel></rss>