<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Kanwar Kohli</title>
    <description>The latest articles on DEV Community by Kanwar Kohli (@kanwar_kohli).</description>
    <link>https://dev.to/kanwar_kohli</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3929700%2F52519bac-2d85-4f66-af47-5306edcca82c.png</url>
      <title>DEV Community: Kanwar Kohli</title>
      <link>https://dev.to/kanwar_kohli</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/kanwar_kohli"/>
    <language>en</language>
    <item>
      <title>Built a small tool that tells you why your AWS bill changed each week</title>
      <dc:creator>Kanwar Kohli</dc:creator>
      <pubDate>Wed, 13 May 2026 16:03:47 +0000</pubDate>
      <link>https://dev.to/kanwar_kohli/built-a-small-tool-that-tells-you-why-your-aws-bill-changed-each-week-3klo</link>
      <guid>https://dev.to/kanwar_kohli/built-a-small-tool-that-tells-you-why-your-aws-bill-changed-each-week-3klo</guid>
      <description>&lt;p&gt;Over the past year I kept seeing the same AWS problem across founders and small engineering teams: the bill changes faster than people can explain it.&lt;br&gt;
Usually nobody notices until month-end, and by then they're digging through Cost Explorer trying to figure out which service changed, what deployment caused it, and whether it's real growth or waste.&lt;br&gt;
So I built a lightweight tool called ThinCost.&lt;br&gt;
It connects to AWS using a read-only IAM role and sends a weekly email explaining what changed, which services drove the increase, potential waste, and concrete actions to reduce spend.&lt;br&gt;
The goal wasn't another dashboard. It was: "Tell me in plain English why my AWS bill changed."&lt;br&gt;
Setup is about 60 seconds: email + AWS account ID → deploy a CloudFormation stack → done. No stored credentials. No write access. Read-only permissions only.&lt;br&gt;
Looking for a handful of beta testers running real AWS workloads. Happy to give free access for a few months in exchange for honest feedback.&lt;br&gt;
→ thincost.com&lt;/p&gt;

</description>
      <category>aws</category>
      <category>monitoring</category>
      <category>showdev</category>
      <category>tooling</category>
    </item>
  </channel>
</rss>
