AWS Cloud Financial Management

In this post, we introduce the Kiro Cost Optimizer, an open-source, serverless solution that gives you per-developer visibility into Kiro Enterprise credit usage. It ingests Kiro’s daily per-user activity reports, accumulates month-to-date usage per developer, and delivers a consolidated usage visibility report with tier optimization recommendations via email on a schedule you control. The entire stack deploys in minutes with a single AWS CloudFormation template, costs less than a few dollars a year to operate, and requires zero ongoing maintenance.

If you are managing a multi-account AWS Organization, you might have noticed that Savings Plan recommendations differ between management account (also known as payer account) and member account (also known as linked account). Consider this scenario: you are reviewing Savings Plan recommendations in the AWS Billing and Cost Management Console. At the management account level, you see a recommended commitment of $100 per hour for a one-year no-upfront Compute Savings Plans. However, when you switch to the member account view, the recommendations total only $70 per hour. This blog post explains these differences and shares best practices for making informed decisions on purchasing Savings Plans.

This blog post helps you measure what your coding work costs across the models, harnesses, and hosting paths available to you, so you can turn the measurements into a cost-and-quality frontier, and put that frontier in front of developers before they choose a model.

FinOps practitioners used to spend hours on manual cost analysis and reporting. Today, tooling such as the AWS FinOps Agent, AI-powered cost investigations, and Amazon Q Developer cost capabilities can trace costs to a specific resource and surface opportunities in minutes. But without someone providing business context, they’re just numbers. As AI increases both speed […]

At this year’s re:Invent, we’ve lined up a fantastic set of sessions to get you up to speed on the latest AI cost management frameworks, solutions, and real-life success stories. They will help you wrap your head around concepts, such as tokenomics, and get ahead of the AI cost management game. Across tracks, more than 30 sessions fall under the theme of cloud financial management and AI cost management. In this blog post, I highlight nine of them and share where you can find AWS FinOps experts and peers throughout the week.

In this first part of our two-part series, you’ll create a Workload Estimate to compare the compute costs of Amazon Elastic Compute Cloud (Amazon EC2) instances on x86 processors against the same instances on AWS Graviton processors. This post covers cost modeling for migration planning, not migration execution steps. Part two of this series will cover Bill Estimates in depth.

If you manage Enterprise Support for a large AWS organization, you’ve likely been asked which accounts a single Support line item comes from and how it was calculated. These are the questions the AWS Billing API can now answer programmatically. This post shows you how to break down your monthly AWS Enterprise Support charge by account using three AWS Billing API operations.

Tokens are the currency models work in. Every model takes tokens as input and produces tokens as output, and those tokens can come from anywhere: a person typing a prompt, an application making a call, or another AI agent talking to your model through an MCP server. In this blog, we focus on the tokens generated by AI coding tools and AI solutions. If you’re a FinOps practitioner trying to get ahead of AI spend, you need a framework to work from. That’s what this blog is for. We’re going to use the AWS Cloud Financial Management (CFM) pillars you may already know, See, Save, Run, and Plan, but with a tokenomics lens. They will be Visibility & Attribution, Optimization, Governance, and Value/ROI. We have created a landing page going deeper into these subjects on the Tokenomics CFM Tips page.

As organizations scale their cloud footprint, they also need a mechanism to effectively scale their cost optimization practice at the same time, which is where FinOps Experience-Based Acceleration (EBA) workshop come in to scale the process efficiently. Cost visibility tools identify savings, however many organizations struggle to turn those insights into action across their hundreds of teams and thousands of applications. This post discusses the best-practices that a major North American financial institution took to run a FinOps EBA to scale their cloud cost optimization and establish a cost-aware culture across their organization; this resulted in generating over $1.4M USD in annual recurring savings for them.

When you use AWS Billing Conductor (ABC) to produce pro forma billing, you have full control over how costs are presented to your member accounts. By default, commitments purchased at the management account level are managed separately from ABC billing groups. Pro forma bills for your member accounts reflect on-demand equivalent costs. The good news is that ABC provides the flexibility to customize your pro forma billing to reflect these savings, which sometimes requires additional configuration beyond the default setup. In this post, we walk you through an automated pipeline that calculates the exact dollar savings each member account received from management-held RIs and SPs and injects those savings as proportional credit adjustments into ABC. This gives you an accurate, auditable chargeback number for every account, every month.