Skip to content
← module.projects

Estate cost review

Finding the spend nobody had claimed.

Year
2025
Discipline
FinOps
Stack
AWS Cost Explorer · CloudWatch · Python · Terraform

—%

Monthly spend reduced (replace)

100%

Resources with an owner tag

Weekly

Cost report to each team

the problem

Placeholder. Monthly AWS spend had grown steadily with no owner per line item. Nothing was obviously wasteful, which is what made it hard.

what I built

  1. 01

    Introduced a mandatory tagging policy and backfilled tags across existing resources.

  2. 02

    Built a report that maps spend to team and environment rather than to service.

  3. 03

    Right-sized instances against observed load and moved non-production off on a schedule.

architecture

Resources, by tier

Collection

+aws_cur_report_definition

+aws_s3_bucket.billing

Processing

+aws_lambda_function.tag_audit

Reporting

+aws_sns_topic.cost_weekly

next project

Multi-account landing zone