A cloud cost dashboard puts several saved cost reports on one surface for a recurring reader or workflow, such as an engineering team's weekly review or finance's monthly check. It is for reading and deciding, not a record: every tile computes on the data as it stands at the moment someone looks. It matters for the bill because it decides which movements someone sees regularly and which they never see. A FinOps dashboard that shows everyone everything answers nobody's question.
How it works
Every tile is a report with its own scope, period, cost basis and filters (cost reports and saved views). The dashboard adds the choice of questions for one reader and, depending on the tool, a shared period. The three large providers offer different things for it.
AWS
The Billing and Cost Management console has dashboards of its own: collections of widgets with data from Cost Explorer, Savings Plans and Reserved Instance utilisation and coverage, AWS Budgets, cost efficiency and detected anomalies. A dashboard holds up to 20 widgets, an account up to 50 dashboards. Each widget saves its own filters, grouping, granularity and period; a dashboard-level period applies only temporarily and resets when you leave or refresh the dashboard. AWS provides five read-only Managed Dashboards, Cost Overview & Trends among them; to adapt one, you duplicate it. Sharing runs through AWS Resource Access Manager, with accounts inside or outside the organisation, read-only or with edit rights. Only the configuration travels, not the data: recipients see figures according to their own permissions, but they see every filter value, account numbers, tag keys and tag values included. Dashboards export as PDF or go out by email as a scheduled PDF, widget data exports as CSV. AWS states that charges for the current billing period are estimates and that dates are in UTC.
Azure
In cost analysis, a view can be pinned to a dashboard in the Azure portal. Only the main chart or table lands on the dashboard, as an entry point back into cost analysis. The tile holds a copy of the configuration; later changes to the saved view reach it only when the view is pinned again. Portal dashboards are private when created, up to 100 per user. A published, shared dashboard is an Azure resource in a resource group, and Azure RBAC decides who may view or edit it. Each tile checks permissions on its own data; someone allowed to see the dashboard still sees nothing in a cost tile without a role on the cost scope.
Google Cloud
For the billing console Google documents two ready-made overviews: Cloud Billing reports with saved reports, and the FinOps hub, which automatically gathers current savings and optimisation opportunities on one surface. Dashboards of your own are built on the BigQuery export, for instance in Data Studio, as Looker Studio is now called, or in Looker, for which Google presented a template based on FOCUS 1.0 in 2024. Google recommends pointing reports and dashboards at BigQuery views rather than the export tables, so that schema changes in the export do not break the queries. A Data Studio report on BigQuery can itself incur query or storage charges. What the export contains is covered in Google Cloud billing export: datasets and fields.
What it means for your cost
A dashboard answers the question of who sees which movement early. It is therefore built from the reader, not from the data. The reader column follows the core personas in the FinOps Foundation's FinOps Framework (CC BY 4.0), one FinOps persona per row; what each one decides is covered in core and allied personas in the FinOps framework.
| Reader | Question | Tiles | Cost basis and period |
|---|---|---|---|
| Engineering | What moved in our services since yesterday or last week? | daily cost by service and environment, anomalies, commitment coverage | amortised or effective, days, rolling |
| Finance | Does the month match the invoice, and where does it stand against budget? | total per invoice and billing account, budget against actual, credits | billed, closed months with fixed dates |
| Leadership | Where are total cost, forecast and unit cost heading? | total against budget and forecast, a few drivers, unit cost | one stated cost basis, months |
| Product | What does a product, a feature, a customer cost? | cost per product segment, unit cost | effective, months |
What management and finance need beyond that is covered in reporting for management and reporting for finance; unit cost in unit economics and unit costs.
Three rules keep a dashboard readable. One cost basis per dashboard, or visibly per tile, because billed and amortised cost side by side show the same reservation purchase once as a spike and once spread out. One period per dashboard, or visibly per tile. And a visible data cut-off, because the current month is estimated and changes until finalisation. For the month-end close the dashboard does not count; the saved report with fixed dates or the export does. Console dashboards also see only their own provider; putting several clouds on one surface takes a shared data basis in one currency (multi-cloud reporting in one currency). Bringing the surface to readers without console access takes a delivery (report subscriptions and delivery).
Where it goes wrong
- Mixed cost bases. Symptom: one tile shows a spike in January, the tile next to it does not, and both are labelled "cost". Cause: one computes billed cost, the other amortised.
- Mixed periods. Symptom: the team tiles do not add up to the total tile. Cause: the widgets have their own periods; on AWS the dashboard period applies only temporarily, while the widgets' periods are what is saved.
- A stale tile. Symptom: the pinned Azure tile shows filters long since changed in the view. Cause: the tile is a copy and stays old until it is pinned again.
- An estimate taken as the result. Symptom: the month on the dashboard differs from the invoice. Cause: the current period is estimated, and AWS notes that estimates can differ from actual charges.
- Too much shared. Symptom: an external account sees account numbers and tag values. Cause: AWS shares the configuration with every filter value in it.
- Empty tiles. Symptom: a shared dashboard shows a reader no figures. Cause: access to the dashboard is not access to the cost data; AWS and Azure check the two separately.
Sources
Read on 2026-10-16. AWS dashboards, getting started and permissions, adding widgets, customizing dashboards, available Managed Dashboards, sharing dashboards, exporting dashboards and quotas and restrictions; Microsoft save, share and pin views, dashboards in the Azure portal and sharing access to dashboards; Google Cloud FinOps hub, Cloud Billing reports, export Cloud Billing data to BigQuery, connect Data Studio to BigQuery and the Looker template for FOCUS; FinOps Foundation personas (CC BY 4.0).