<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>CloudWatch on The David Page</title><link>https://thedavidpage.pages.dev/posts/cloud/aws/cloudwatch/</link><description>Recent content in CloudWatch on The David Page</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Tue, 05 May 2026 09:00:00 +0700</lastBuildDate><atom:link href="https://thedavidpage.pages.dev/posts/cloud/aws/cloudwatch/index.xml" rel="self" type="application/rss+xml"/><item><title>That CloudWatch Logs Insights Query Just Cost You $2.50</title><link>https://thedavidpage.pages.dev/posts/cloud/aws/cloudwatch/cloudwatch-logs-insights-expensive-queries/</link><pubDate>Tue, 05 May 2026 09:00:00 +0700</pubDate><guid>https://thedavidpage.pages.dev/posts/cloud/aws/cloudwatch/cloudwatch-logs-insights-expensive-queries/</guid><description>&lt;p&gt;&lt;strong&gt;One click on CloudWatch Logs Insights, a few seconds waiting for results — and a bill for scanning half a terabyte of logs.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Hi everyone 👋&lt;/p&gt;
&lt;p&gt;CloudWatch Logs Insights is a genuinely convenient SQL-like log query tool. The way AWS bills for it, though, catches a lot of people off guard.&lt;/p&gt;
&lt;h2 id="-the-common-mistake"&gt;😱 The common mistake&lt;/h2&gt;
&lt;p&gt;Open Logs Insights, pick a log group that&amp;rsquo;s accumulated 6 months of logs (~500 GB), type a broad search query with no explicit time range set, hit &lt;strong&gt;Run&lt;/strong&gt;.&lt;/p&gt;</description></item></channel></rss>