Cloud FinOps · AWS · Data Analysis
As a Cloud FinOps Consultant at Accenture. I work at the intersection of data analysis and cloud economics, turning complex billing data into actionable cost-saving strategies.
AWS embedded Amazon Q directly into Cost Explorer nine days ago. You can now type plain English questions and the visualisations update automatically. Most coverage has been technical. This is the practitioner's version — the specific prompts to run, in the order to run them, for a complete cost analysis from morning review to executive reporting.
April 15, 2026
S3 Files launched four days ago. S3 Vectors went GA at re:Invent. Object size limits jumped from 5TB to 50TB. Account-regional namespaces removed a naming constraint that has existed since 2006. AWS has made more changes to S3 in the past five months than in the previous five years. Some of these changes are technical. Several of them have direct cost implications your team may not have modelled yet.
April 11, 2026
Six years of the FinOps community asking for this. AWS delivered it at re:Invent 2025. The headline says 'up to 35% savings' — the reality is more complicated, more interesting, and more useful than the press release suggests.
March 20, 2026
Enterprise / Multi-Account AWS
A large AWS organisation had been doing FinOps right on paper. Cost Explorer configured, budgets set, alerts in place. But 38% of their total cloud spend was completely untagged. No business unit. No application. No environment. $2.5 million a year that finance couldn't attribute, and that nobody owned. The problem wasn't technical. It was that nobody with authority had ever seen the number.
Manufacturing / Industrial
A manufacturing company's Athena costs exploded to nearly 10x their baseline in a single billing cycle. Their data team was doing everything right — real-time streaming, live dashboards, instant insights from the factory floor. They just had no idea what it was costing them to do it.