Arkinu
AWS service comparison

AWS Cost and Usage Report vs AWS Cost Explorer: differences and when to use each

AWS Cost and Usage Report
AWS Cost Explorer

Often confused on the examQuestions tend to offer one as a distractor for the other: look for the phrase in the scenario that tips the balance.

AWS Cost Management

AWS Cost and Usage Report

The most comprehensive set of AWS cost and usage data: it publishes detailed billing reports to an Amazon S3 bucket, broken down by hour, day, or month, and by product, resource, or tags. The reports can be queried with Amazon Athena or loaded into Amazon Redshift.

Exam phrases that point here

  • «the most detailed cost and usage report, by the hour and by resource»

    The AWS Cost and Usage Report is the most detailed billing dataset in AWS: it can be broken down by hour, day, or month, by product, by resource, and by tags.

    When not: If viewing trends and grouping spend in charts is enough, without processing files, AWS Cost Explorer is more direct. If you want an alert when an amount is exceeded, it is AWS Budgets.

  • «deliver billing data to an Amazon S3 bucket for processing»

    The report is exported to your own S3 bucket, at least once a day, in CSV or Parquet, ready for other tools to read.

    When not: Today it is created as an AWS Data Exports export (CUR 2.0); the legacy CUR still exists but with a different API. If the question is about API call records and not about costs, the answer is AWS CloudTrail.

  • «query costs with SQL»

    With the report in S3 in Parquet format, an AWS Glue crawler creates the table and Amazon Athena lets you query it with serverless SQL; it can also be loaded into Amazon Redshift.

    When not: If business users want visual dashboards rather than writing SQL, the pattern is a dashboard in AWS Quick Sight (formerly Amazon QuickSight) on top of that data. For a one-off look at spend, Cost Explorer avoids building this pipeline.

  • «split the cost of instances among the containers that run on them»

    Split Cost Allocation Data assigns each Amazon ECS container (and AWS Batch jobs) a share of the EC2 instance cost based on its CPU and memory usage, and reflects it in the Cost and Usage Report.

    When not: It has to be turned on from the management account or a standalone account; without that option the report only shows the cost of the whole instance. To split by team or project without containers, cost allocation tags are enough.

Often paired with

  • Amazon S3
  • Amazon Athena
Study AWS Cost and Usage Report →

AWS Cost Management

AWS Cost Explorer

Tool for viewing and analyzing your AWS costs and usage with charts and reports. It shows up to 13 months of history by default (extendable to 38 months with monthly data), forecasts spend for the next 18 months, and recommends which Reserved Instances to purchase.

Exam phrases that point here

  • «visualize and analyze the costs of the past few months by service or by account»

    AWS Cost Explorer shows cost and usage in charts and reports, with up to 13 months of history by default (extendable to 38 months with monthly data), and lets you filter and group by service, Region, or member account without setting anything up.

    When not: If you need line-by-line detail, by the hour and by resource, to load into your own tools, the answer is the AWS Cost and Usage Report (through AWS Data Exports). If you want an alert when an amount is exceeded, it is AWS Budgets.

  • «find out how much each team or project spends based on their tags»

    With cost allocation tags turned on, Cost Explorer can filter and group spend by those tags, for example project or cost center.

    When not: The tags must be applied to the resources and activated in the billing console; before that they do not appear in the analysis. If you also want to split the cost of Amazon ECS containers based on their consumption, you need the detail of the Cost and Usage Report.

  • «forecast spend for the coming months based on historical usage»

    Cost Explorer calculates a forecast based on past spending patterns: monthly up to 18 months and daily up to 3 months.

    When not: If the goal is to act when a forecasted spend is reached (alert or restrict), that is configured in AWS Budgets. To estimate the cost of an architecture that does not exist yet, AWS Pricing Calculator is used, not Cost Explorer.

  • «recommendations on which Reserved Instances or Savings Plans to purchase»

    Cost Explorer analyzes historical usage and recommends Reserved Instance purchases and the right Savings Plans commitment, and then shows utilization and savings reports.

    When not: If the question is whether the instances are the right size (rightsizing) and not which commitment to buy, AWS Compute Optimizer gives more specific recommendations. The discount itself comes from the Savings Plan or the Reserved Instance, not from Cost Explorer.

Study AWS Cost Explorer →