AWS ships five ready-made FinOps dashboards inside its billing console
On August 14, 2026, AWS added preconfigured, read-only managed dashboards to Billing and Cost Management, at no extra cost. It is the baseline FinOps visibility the vendor is finally offering natively — and direct pressure on third-party tools whose entry price starts at 5% of spend.
August 14, 2026. AWS announces Managed Dashboards inside Billing and Cost Management, the billing console. Five dashboards, preconfigured, read-only, populated automatically with the account’s data. No extra cost, across all commercial regions.
The move is plain: AWS is productizing FinOps visibility natively, in a space that was until now the territory of third-party tools — Vantage, CloudHealth, Cast.ai — priced as a percentage of spend. For a team with no cost dashboard at all, the entry point just dropped to zero dollars.
What the five dashboards actually contain
The Managed Dashboards are maintained, read-only dashboards that appear in the console’s dashboard list. They are pre-populated with your account data — no setup, no data-source wiring, no query to write.
- Cost Overview & Trends tracks spending by service, account and region over 12 months, with forward-looking forecasts.
- Compute and Database break down spend within each service category, pairing cost breakdowns with commitment coverage and utilization metrics — the visibility that was missing to connect a bill to its Reserved Instances and Savings Plans.
- Reservations and Savings Plans shows how your purchased commitments are performing across all eligible services, quantifying gaps and underutilization in monetary terms.
Their value rests on a detail that is rarely highlighted: everything is duplicable. A managed dashboard can be copied into a fully editable custom version, its widgets can be added to your existing dashboards, and the whole thing exports to PDF or CSV. AWS understood that a FinOps team’s first reflex is to edit — and anticipated it rather than locking the door.
The strategic read: AWS pushes back on the FinOps market
The announcement does not stand alone. It belongs to a positioning battle that has simmered for years between native and third-party tooling.
Tools like Vantage charge 5% of managed spend beyond a free tier, and their central pitch has always been to spare you each cloud’s cost explorer. AWS answers by building visibility directly into the console, for free, and keeping it maintained — which strips the third party of part of its reason to exist for simple single-cloud accounts.
But the field stays bounded, and it is worth saying so clearly. The Managed Dashboards are single-cloud, read-only, and lack the features that justify the price of specialist tools: multi-cloud aggregation, anomaly detection, automated Savings Plans purchasing, chargeback by business unit. On those fronts, FinOps remains a tooling discipline, not a console feature.
What they do not do: optimize for you
Resist a hasty reading. A dashboard shows; it does not optimize. The three phases of the FinOps Foundation framework — Inform, Optimize, Operate — are not covered equally: these dashboards cover the first, visibility, and lay the foundation for the other two without automating them.
Rightsizing an instance, buying a Savings Plan at the right moment, reselling an underused commitment: none of this is triggered by the Managed Dashboards. They tell you where the waste sits — coverage gaps and underutilization are priced in money — but the action stays manual.
# The same data the dashboards surface is queryable through the Cost Explorer API
aws ce get-cost-and-usage \
--time-period Start=2026-08-01,End=2026-08-16 \
--granularity MONTHLY \
--metrics UnblendedCostThat command returns the period’s unblended cost — the base brick the five dashboards aggregate and contextualize with commitment metrics. The fact that it is stable and documented is what has long made home-grown dashboards possible; what is new is that AWS now ships a maintained version that requires no development.
Who this is for, and when
The positioning resolves along two axes: the team’s FinOps maturity and the cloud perimeter.
For a team with no cost dashboard at all — the majority of organizations below a certain volume — the Managed Dashboards are the fastest and cheapest possible answer: five views, zero setup, zero dollars. For a multi-cloud account or a team that has already industrialized FinOps, they do not replace Vantage or Cast.ai; they complement them, offering a reliable native view alongside the third-party tool.
The maintenance variable also tilts toward native: a dashboard maintained by AWS does not break when the billing API evolves, whereas a home-grown dashboard demands constant watch. Small teams tend to underestimate that argument.
The open FOCUS standard — the FinOps Foundation specification that normalizes billing formats — illuminates the native boundary: these five dashboards do not reconcile your AWS costs with those of Azure, GCP or your SaaS into a single view. As long as your spending is concentrated on one cloud, the console is enough; the moment multi-cloud enters the picture, normalization becomes exactly the job a third-party tool charges for.
That points to a clean decision sequence. The native cost is zero, but its perimeter stops at the edge of the AWS account. Most teams should follow the path the FinOps Foundation calls crawl-walk-run: start with the free managed dashboards to see, then graduate to a paid tool only when you outgrow the native boundary — when you add a second cloud, when you need anomaly alerts wired into Slack, or when you want Savings Plans bought for you automatically. Buying the tool before you have the visibility is paying for a discipline you have not yet built.
The counter-argument — that AWS could later restrict or paywall what is now free — deserves a hearing, but it cuts the other way here. Cost visibility is a retention feature for AWS, not a revenue line: a customer who can see their own waste is a customer who keeps spending, and the third-party market has spent years proving the demand. The more likely trajectory is that AWS expands these dashboards, not that it gates them.
Where managed dashboards stop, and dedicated tools begin
To place the announcement, set it inside AWS’s billing portfolio, which is not limited to these five dashboards. Cost Explorer already exposes cost and forecast analysis; AWS Budgets sends threshold alerts; Cost Anomaly Detection flags unusual spikes; Cost Categories groups costs by business unit for chargeback. The Managed Dashboards sit on top of those bricks with a ready-made presentation layer — they replace none of them.
That is exactly what bounds their reach. Anomaly detection remains a separate feature you must enable and interpret; chargeback still requires configuring Cost Categories first; automated Savings Plans purchasing simply does not exist natively. A managed dashboard tells you that you are wasting money on underused commitments; it does not fix it.
For a single-cloud account early in its FinOps maturity, this native ecosystem covers most of the “Inform” phase. For a multi-cloud account or a team that wants automation, the native boundary is reached quickly — and that is where third parties regain the advantage.
Verdict
If you still have no cost visibility on AWS, open the Billing and Cost Management → Dashboards console and read the five Managed Dashboards before buying anything. It is free, immediate, and covers three-quarters of what the “Inform” phase of FinOps needs.
If you operate across multiple clouds, keep your multi-cloud tool — Vantage or equivalent — and add the Managed Dashboards as a native complement. They replace neither multi-cloud aggregation nor commitment automation.
The bigger signal is that native is eating third-party from the bottom of the market: what was a sold product is becoming a console feature. The consequence for FinOps vendors is already legible — they will have to justify their 5% of spend with what the console does not do: automation and multi-cloud.