Articles

Buried inside the AgentCore announcements at AWS Summit New York is a detail that most of the coverage walked straight past. AWS agents can now autonomously pay for APIs, paywalled content, and other agents using stablecoin settlement in 200 milliseconds, with no human approving the transaction. AWS called it a cost category most enterprise teams haven't budgeted for. They're right. Here's why this is the next FinOps governance problem, and why the usual playbook doesn't cover it.

On June 9, AWS shipped the autonomous cost agent I wrote about after Day 1 of FinOps X. It investigates cost anomalies, answers questions in Slack and Jira, and opens tickets on your behalf. The demo is impressive. The preview, according to the practitioners who have actually deployed it, has real rough edges. Here's the honest gap between the announcement and the reality.

Day 2 of FinOps X presented a Crawl, Walk, Run model for agentic FinOps maturity, announced FOCUS 1.4, and featured Google, Oracle, IBM, and Flexera shipping autonomous cost management features. Mike Fuller's line — AI won't take FinOps jobs, but practitioners who know AI better will , was the most important thing said at this conference. Here's what Day 2 delivered, what I think it means, and what the community isn't saying out loud.

Day 1 of FinOps X 2026 opened with a new discipline, a new foundation, and the most significant AWS product announcement in the CFM space in two years. The Tokenomics Foundation intent was announced. AWS shipped an autonomous FinOps Agent. And somewhere between those two things, the role of the FinOps practitioner quietly shifted.

FinOps X opens in San Diego on June 8. AWS will be there with senior leadership, a hands-on GameDay, and almost certainly a set of product announcements. Based on what's been building in the CFM space over the past six months and where the community's attention sits heading into the conference, here's what's worth paying close attention to — and what's likely to get announced while everyone is looking elsewhere.

For years, Reserved Instances and Savings Plans in AWS applied across your entire organisation by default. The team that bought the commitment didn't always get the discount. Finance corrected it manually every month. AWS launched RISP Group Sharing in November 2025 and that problem now has a real fix. Here's what actually changed, how the two modes work in practice, and what to check before you enable it.

AWS launched granular cost attribution for Amazon Bedrock sixteen days ago. You can now see exactly which IAM principal called which model and what it cost, directly in CUR 2.0 and Cost Explorer. This is the first time that's been possible. For FinOps teams trying to govern AI spend before it becomes ungovernable, here's what the feature does, how to set it up, and where it still falls short.

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.

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.

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.

RDS Reserved Instances are fundamentally different from EC2 RIs in ways that catch even experienced teams off guard. Here's what goes wrong, why it's harder to fix than you'd expect, and what your options actually are.

From Reserved Instances to rightsizing, here are the five highest-impact strategies to reduce your AWS bill without sacrificing performance.

The FinOps Foundation's framework gives cloud teams a shared language and operating model for managing cloud spend. Here's how to apply it in practice.