1. Resources
  2. Guides & tutorials

Guide · 4 min read · Published October 2024

Cloud cost dashboard in Tableau using AWS cost data

Cloud spend grows when nobody watches it. A Tableau dashboard of AWS cost data, read with the Well-Architected Framework, shows where to cut waste.

A cloud cost dashboard in Tableau shows how AWS resources are used so you can find waste and keep spending predictable. Use it with the AWS Well-Architected Framework, especially Cost Optimization, to review usage, tags, and cost over time. The same principles apply to Azure and Google Cloud.

Why Cost Optimization cuts cloud waste

The AWS Well-Architected Framework is a blueprint for designing and operating cloud environments. Cost Optimization, one of its pillars, is about cutting waste, using resources more carefully, and keeping cloud spending predictable.

Tableau shows how cloud resources are actually used, and where the savings are. Together they help you:

  • Improve profitability by finding opportunities to spend less.
  • Raise operational efficiency by improving how resources are allocated.
  • Make decisions from the data that line up with the goals of the business.

The six pillars of the framework

Cost optimization is one of six.

  • Operational excellenceRunning and monitoring systems to deliver business value and continually improving processes and procedures.
  • ReliabilityEnsuring a workload performs its intended function correctly and consistently when it is expected to.
  • SecurityProtecting your information systems.
  • Performance efficiencyUsing IT and computing resources efficiently.
  • Cost optimizationAvoiding unnecessary costs.
  • SustainabilityMinimizing the environmental impacts of running cloud workloads.
The six pillars of the AWS Well-Architected Framework: operational excellence, reliability, security, performance efficiency, cost optimization and sustainability.

How Tableau and the framework read cost data

AWS produces a large volume of data on resource usage and cost. The Well-Architected Framework is the guidance for managing and improving that usage. Tableau turns the data into visuals you can read. Five practices connect the two:

  1. Spot usage trends with Tableau dashboards. EC2, S3, and RDS produce detailed usage data, and dashboards show how that usage moves over time. The framework says to review these patterns regularly and remove resources you do not need. Real-time visuals show when and where resources are used or wasted.
  2. Use custom tags for a closer look. AWS lets you tag resources by team, department, product, or service. Tableau pulls those tags into dashboards so you can track spending at that level. The Cost Optimization pillar encourages tagging so you can see when a team or project is using more than it needs.
  3. Track and compare costs over time. The framework calls for continuous monitoring of cloud costs. Tableau shows cost in real time and across weeks and months. Dashboards can track spikes and drill into a specific service, so the team can follow best practices for cost management.
  4. Put cost controls in Tableau. AWS Cost Explorer and AWS Budgets help set financial controls. Tableau makes those controls easier to see, with alerts and dashboards that flag when spending crosses a threshold, so you can act before it runs past the plan. To get the data into Tableau, AWS Data Exports (CUR 2.0) delivers detailed cost and usage data to S3.
  5. Keep optimizing as you grow. The framework asks you to keep improving the cloud setup as the business grows. Tableau shows usage and cost as they change. If an EC2 instance is underused, it shows up on the dashboard, and you can downsize it or turn it off.

Five ways Tableau and the framework work together

From spotting trends to continuous optimization.

  1. Spot usage trends

    With Tableau dashboards.

  2. Use custom tags

    For detailed analysis by team, department, product or service.

  3. Track and compare costs over time

  4. Implement cost controls

    With alerts and dashboards in Tableau.

  5. Continuously optimize for growth

The five ways the article describes Tableau and the AWS Well-Architected Framework working together on cloud costs.

How an AWS organization is structured

Policies flow down from the organization to the accounts.

  1. Root account

  2. AWS Organization

  3. Organizational units

    Each with a tagging policy and a service control policy.

  4. Accounts

The structure shown in the original diagram: a root account, the AWS Organization, organizational units with a tagging policy and a service control policy, and the accounts beneath them.

What the four dashboard pages show

An example dashboard built by Marcelo Has is one way to see this in practice. It leads with a few metrics and lets you drill further:

  • Overview. Unit cost, usage cost, and order quantity, plus variance by billing account and by team (custom tags). It highlights the top two areas driving cost fluctuations, so a decision-maker can see where to act.
  • Account. Usage cost, and how much of that cost is tagged for analysis. Drill into AWS services, teams, internal company services, and data transfer. Variance trends show detail by team and by internal company service.
  • Team. The same structure as the account page, focused on one team. A tagged metric shows how much of cloud resource cost is tagged correctly, so the team can monitor its own usage.
  • Service. Cost over time, which is how you find outliers and unexpected spikes. Teams can see unusual increases in AWS services and act before the increase hits the wider budget.

This kind of dashboard is how a business uses Tableau to manage cloud cost. It shows resource usage in a form the team can read, aligns cloud decisions with Well-Architected principles, and keeps spending in check.

The overview page

The metrics the dashboard's first page leads with.

Overview · Cloud costsExample data
An example cloud cost overview with four tiles: unit cost, usage cost, order quantity and the share of resources that are tagged. The numbers are examples.

Usage cost by service

Where drill-down starts.

Usage cost by serviceExample data
An example progress list of usage cost for the AWS services the article names: EC2, S3, RDS and data transfer. The numbers are examples.

How cost control supports profit and growth

Tableau alongside the AWS Well-Architected Framework helps most when the business is growing.

  • Profitability. The visuals, read with the framework’s cost practices, show where cloud cost can come down. Those savings improve profit by removing waste and by using cloud resources more carefully.
  • Operational efficiency. The Operational Excellence and Cost Optimization pillars both stress how resources are allocated. Tableau lets teams see usage clearly, which makes inefficiency easier to find and the operation easier to improve.
  • Growth. Cloud usage rises as the business grows. Tableau lets you watch those changes and the cost pattern over time, so scaling is a decision you can defend. Follow the framework, and read Tableau’s cost and usage views, before you change allocation or controls.

Tableau and the AWS Well-Architected Framework are how you manage cloud cost: see how resources are used, then make the financial decision from that view. As usage grows, that discipline keeps spending under control while the business focuses on growth, profitability, and innovation.

Schedule a free consultation to walk through a cloud cost dashboard.

Marcelo Has

01 FAQ

Frequently asked questions

What does a cloud cost dashboard in Tableau show?

The overview leads with unit cost, usage cost, and order quantity, plus variance by billing account and team tags. It also highlights the top two areas driving cost fluctuations. The account and team pages focus on usage cost, how much of that cost is tagged, and drill-down by service, team, internal company service, and data transfer. The service page tracks cost over time so outliers and spikes show up before they affect the budget.

How does the AWS Well-Architected Framework help with cloud cost?

Cost Optimization is about cutting waste, using resources more carefully, and keeping cloud spending predictable. The framework recommends a regular review of usage, tagging, continuous monitoring, and ongoing optimization as the business grows. Tableau supplies the dashboards that make those reviews visible.

How should cloud resources be tagged for cost analysis?

Custom tags group resources by team, department, product, or service. Tableau pulls those tags into dashboards so you can see spend at that level. The Cost Optimization pillar encourages tagging so you can tell when a team or project is using more than it needs.

How do Tableau and AWS budgets flag a cost spike?

AWS Cost Explorer and AWS Budgets help set financial controls. Tableau shows those controls and can alert you when cloud spending crosses a threshold you set. AWS Data Exports (CUR 2.0) delivers the detailed cost and usage data to S3 so Tableau can use it.

Does this cloud cost approach apply only to AWS?

AWS is the worked example, including EC2, S3, and RDS. Companies also rely on Azure and Google Cloud. The same principles apply to those providers.