https://aws-sensei.cloud/tags/athena/Athena - Tag - AWS SenseiHugo -- gohugo.ioenThu, 28 May 2026 00:00:00 +0200https://aws-sensei.cloud/posts/2026-05-28-analytics-cost-optimization/Thu, 28 May 2026 00:00:00 +0200Marcelhttps://aws-sensei.cloud/posts/2026-05-28-analytics-cost-optimization/🔊 Voiced by Amazon Polly $4.64 in two days. For a blog with modest traffic, that’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.https://aws-sensei.cloud/posts/2026-05-18-privacy-analytics/Mon, 18 May 2026 00:00:00 +0200Marcelhttps://aws-sensei.cloud/posts/2026-05-18-privacy-analytics/🔊 Voiced by Amazon Polly Google Analytics is the obvious choice for blog analytics — free, ready to go, works out of the box. But it also means: third-party cookies, data sharing with Google, and a consent banner you have to make GDPR-compliant somehow. For a blog about AWS, it seemed natural to solve this differently. The result: a custom analytics system built from three AWS services that sets no cookies, stores no IP addresses, and respects DNT — with a live dashboard at /stats.