
DriftSpend¶
DriftSpend is a lightweight, serverless cost‑analytics solution designed to give you fast, automated visibility into your weekly AWS cloud spend — without dashboards, heavy infra, or manual Cost Explorer clicks.
It collects daily cost data, aggregates and analyses it weekly, and delivers a clean HTML report straight to your inbox. An optional static dashboard provides a secure way to explore the latest results.
Why I Built DriftSpend¶
Working daily with AWS, I wanted a simple, automated way to stay on top of cloud costs across regions — without having to log into the AWS console, click through Cost Explorer, or remember to check dashboards.
The problem was simple:
- AWS billing data is powerful but not proactively delivered.
- Costs can drift quietly, especially in multi‑region setups or during development spikes.
- Dashboards require manual effort and context switching.
So I built DriftSpend as a lightweight, low‑maintenance solution:
- It collects and analyses spend automatically.
- It sends a clean, mobile‑friendly weekly email, so insights come to me — not the other way around.
- It adds optional dashboards only when needed, keeping the workflow lean and efficient.
DriftSpend trims away the noise I don’t need and delivers exactly the visibility I want.
What DriftSpend Provides¶
📡 Automated Cost Collection¶
A daily Lambda job queries AWS Cost Explorer and stores normalized snapshots in S3.
📊 Weekly Spend Insights¶
A weekly job aggregates data and produces:
- Total spend for the period
- Top services and their contribution
- Regional breakdowns
- 30‑day and 90‑day projections
- Week‑over‑week trends
Delivered via responsive HTML email.
🔒 Secure, Minimal Footprint¶
- Fully serverless (Lambda + S3 + SES)
- No persistent compute
- Private bucket & least‑privilege IAM
- Optional CloudFront‑secured dashboard
📁 Optional Static Dashboard¶
The weekly reporter can publish a small HTML dashboard to S3/CloudFront for at‑a‑glance visibility.
Architecture (At a Glance)¶
Daily collector → S3 snapshots → Weekly reporter → Email + optional dashboard.
See full diagram & explanation in
➡️ architecture.md
Interested?¶
I’m always happy to chat about the project or hear suggestions. 👉 Reach me on LinkedIn or my dev email.