<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Lambda on Build on AWS</title><link>https://buildonaws.lakil.org/tags/lambda/</link><description>Recent content in Lambda on Build on AWS</description><generator>Hugo</generator><language>en</language><lastBuildDate>Tue, 12 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://buildonaws.lakil.org/tags/lambda/index.xml" rel="self" type="application/rss+xml"/><item><title>We Blocked the DDoS, Then the CloudWatch Bill Arrived</title><link>https://buildonaws.lakil.org/posts/ddos-log-auto-filter/</link><pubDate>Tue, 12 May 2026 00:00:00 +0000</pubDate><guid>https://buildonaws.lakil.org/posts/ddos-log-auto-filter/</guid><description>&lt;h1 id="we-blocked-the-ddos-then-the-cloudwatch-bill-arrived"&gt;We Blocked the DDoS, Then the CloudWatch Bill Arrived&lt;/h1&gt;
&lt;p&gt;&lt;strong&gt;TL;DR:&lt;/strong&gt; AWS Shield Advanced protects against DDoS-related scaling costs, but WAF log costs are not covered. When a customer said &amp;ldquo;I need to keep logs but reduce costs,&amp;rdquo; I proposed three incremental steps: (1) switch log destination to Data Firehose for ~8.5x cost reduction, (2) apply a WAF Logging Filter to DROP logs by DDoS label, (3) if logs must be preserved during normal operations, use CloudWatch Alarm + Lambda to automatically toggle the filter only during active DDoS. Step 3 is not a best practice — it is a workaround for specific edge cases.&lt;/p&gt;</description></item></channel></rss>