AWS FinOps Agent (preview)
Investigates cost anomalies to root cause and answers cost questions for engineers across your organization, in the tools you already use
Why AWS FinOps Agent?
AWS FinOps Agent brings specialized cost expertise to every engineer and fits the way your teams already work inside Jira and Slack. It also runs on the cadence the work demands: on a recurring schedule, when an anomaly is detected, or whenever an engineer asks a cost question. It draws on AWS Cost Explorer, Cost Anomaly Detection, Cost Optimization Hub, and Compute Optimizer, its answers reflect the same data your central FinOps team relies on.
Benefits
It reduces time to resolution of cost anomalies and scales FinOps insight to every engineer.
The faster your teams can investigate cost anomalies, the faster they can determine whether those anomalies reflect positive business signals, like growth in a new workload, or opportunities to optimize your environment. A Cost Anomaly Detection alert tells you something changed. AWS FinOps Agent takes the next step automatically: it correlates the cost change with AWS CloudTrail events, identifies the change that drove the anomalies, and produces an investigation summary with the likely root cause and the responsible owner. Optionally, the agent can deliver the findings by opening a Jira ticket or posting to a Slack channel, so the engineer who owns the resource gets the context and can decide what to do next. To focus the agent on what matters most, you can include a filter in your automation prompt, for example, only investigating anomalies above a specific dollar threshold, so your team's attention stays on the highest-impact changes.
AWS FinOps Agent lets engineers ask cost questions in natural language and get answers using your actual cost and usage data. An engineer can ask, "Why did my AWS cost go up last month?" and get a response that identifies the cost changes, the contributing services, and the underlying usage drivers. To tailor the agent to your organization, you can upload context files such as account-to-owner mappings, team definitions, tagging conventions, and review cadences. The agent can leverage this context to interpret questions in your organization's terms, for example resolving "What's the cost of Team X?" to the specific accounts that team owns. Engineers get answers at the moment they need them, and your FinOps team can spend that time on strategic work.
Schedule recurring cost reports (e.g., daily, weekly, monthly) rendered in a downloadable, presentation-ready format in html, pdf, or ppt.
Pull recommendations from AWS Cost Optimization Hub and AWS Compute Optimizer, and summarize them into a Jira ticket so the engineering team can pick up the work in the tool they already use.
Customers
Early customers are using AWS FinOps Agent to run recurring cost reviews, cost anomaly response, and engineer follow-through as continuous operations.
Workday is the enterprise AI platform for HR, finance, and IT. The AI Platform Infrastructure team runs Workday's AI platform on AWS.
“Our AI platform runs across many AWS accounts, and two things eat our team’s time: chasing down cost outliers before they become budget problems, and building the monthly cost reports our leadership reviews. The AWS FinOps Agent helps us do both in one place for our AWS environments. It surfaces potential cost anomalies with the context we need to act on them, and it produces the trend and spend views we used to assemble by hand. What used to take our team hours of manual dashboard work each month now starts from a natural‑language interface. That combination of anomaly detection and reporting in one place is why the agent has quickly become a core part of our cloud operations, not just another tool to maintain."
Serjesh Sharma, Manager, Software Development Engineering, Workday
Convera is a global leader in commercial payments operating in a regulated financial services environment.
"The challenge in our FinOps program is not the big optimizations — it is catching the small, unintended cost changes developers introduce before they compound. The AWS FinOps Agent handles that end-to-end: it detects the anomaly, investigates what changed, and creates a Jira ticket to the engineering team that owns the resource, so the right engineer sees it instead of a shared queue that nobody watches. For a fast-moving engineering organization, that closed-loop workflow is the difference between reactive monthly reviews and continuous cost governance."
Ramesh Singaraj, Infrastructure Engineering and Operations Leader, Convera
Mitre 10 is New Zealand’s largest home improvement retailer. Its platform engineering team is responsible for building and operating the AWS platform that underpins the company’s retail technology, while also managing cloud cost visibility and governance.
“Our platform engineering team plays a dual role. We build and operate the shared AWS platform that other teams run their applications on, and we’re also accountable for how we manage cloud spend. Historically, recurring cost reviews, anomaly investigations, and optimisation checks competed directly with reliability and improvement work.
What the AWS FinOps Agent introduces for us is the ability to define cost investigation and review workflows once, and have those checks run continuously in the background. Activities like identifying anomalies, spotting unused resources, or preparing regular cost insights no longer rely on someone remembering to run them. Instead, relevant findings are surfaced when there’s something that genuinely warrants attention.
For a lean platform team, shifting from manual effort to ongoing, contextual cost insights is a meaningful force multiplier.”
Eduard Kleynhans, Platform Engineering Manager, Mitre 10 New Zealand
AVIV Group operates leading digital real-estate marketplaces across France, Germany and Belgium. Its centralized FinOps team supports hundreds of AWS accounts spanning different business units plus multiple additional shared services.
"Our FinOps team supports hundreds of AWS accounts across different business units, and as we move from a purely centralized model to a hybrid model, our local teams take on more of their own cost work. The hardest part of that transition is that engineer questions such as the difference between on-demand and Savings Plan pricing, how a spend projection was calculated, why a cost anomaly fired, all route back to our small central team before the resource owners can act. The AWS FinOps Agent answers those questions directly for the engineer, grounded in our own account-to-business-unit context. That lets our central team spend its time on chargeback logic, optimization strategy and leadership reporting, rather than on the per-question back-and-forth. For a small FinOps team enabling a large organization, that is exactly the leverage we need to be as effective as possible.“
Jordi Espasa, FinOps Director, AVIV Group
Resources
Use cases
Cloud cost anomalies triage for a lean FinOps team
Your central FinOps team gets paged on cost anomalies, but tracing each one through Cost Explorer, CloudTrail, and tag data takes hours, and the engineer who actually owns the resource is two handoffs away. AWS FinOps Agent runs the investigation when the anomaly is detected, correlates the cost change with AWS CloudTrail events, identifies the change behind the anomalies, and creates the Jira ticket or sends Slack messages directly to the owning team. The on-call FinOps engineer reviews the ticket instead of opening the investigation.
Cost transparency for engineering teams in a hybrid FinOps model
You are moving from a centralized FinOps function to a hybrid model where engineering teams take on more cost accountability, but engineers need to route every question through your central team with explanations on understanding different terminologies. AWS FinOps Agent answers cost questions directly with explanations, identifying the cost changes, the contributing services, and the underlying usage drivers, so engineers get answers at the moment they need them and your FinOps team can spend that time on strategic work.
Cost reporting at the cadence your stakeholders need
Your leadership needs a monthly executive summary, business-unit leaders need weekly chargeback updates, and engineering managers need a daily view of their team's spend. Today, someone on your FinOps team rebuilds each one by hand from Cost Explorer screenshots. AWS FinOps Agent generates each report on its own schedule, renders it in a downloadable, presentation-ready format (html, pdf, or ppt), and delivers it to the right audience.
Surfacing Optimization recommendations
AWS FinOps Agent pulls recommendations from AWS Cost Optimization Hub and AWS Compute Optimizer, and summarizes them into a Jira ticket so the engineering team can pick up the work in the tool they already use.
Did you find what you were looking for today?
Let us know so we can improve the quality of the content on our pages