<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Cost Optimization - Tag - AWS Sensei</title><link>https://aws-sensei.cloud/tags/cost-optimization/</link><description>Cost Optimization - Tag - AWS Sensei</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Thu, 28 May 2026 00:00:00 +0200</lastBuildDate><atom:link href="https://aws-sensei.cloud/tags/cost-optimization/" rel="self" type="application/rss+xml"/><item><title>From 900,000 to 3: Drastically Reducing S3 Costs with Incremental Caching</title><link>https://aws-sensei.cloud/posts/2026-05-28-analytics-cost-optimization/</link><pubDate>Thu, 28 May 2026 00:00:00 +0200</pubDate><author>Marcel</author><guid>https://aws-sensei.cloud/posts/2026-05-28-analytics-cost-optimization/</guid><description>🔊 Voiced by Amazon Polly
$4.64 in two days. For a blog with modest traffic, that&amp;rsquo;s an unexpected surprise in the AWS Cost Explorer. The culprit was easy to find — but the fix took three iterations worth writing down.
The Problem My analytics system is built on Kinesis Firehose → S3 → Athena. A scheduled Lambda runs every hour, queries Athena, and writes the result as JSON to S3 where the dashboard reads it.</description></item></channel></rss>