Skip to content

12 · Cost Management Tools

Domain 4 — Design Cost-Optimized Architectures · 20%

This topic is pure tool-matching: given a need — analyze spend, alert on spend, get the raw data, get recommendations, or attribute cost to teams — pick the right AWS tool. The distinctions between Cost Explorer, Budgets, the Cost and Usage Report, and Trusted Advisor are the whole game.

Core concept

AWS gives you separate tools for separate cost questions. The trick is knowing which verb maps to which tool:

  • See / analyze where money went and forecast trends → Cost Explorer
  • Alert / cap when spend crosses a threshold → AWS Budgets
  • Get the most granular billing data for custom analysis → Cost and Usage Report (CUR)
  • Get recommendations to cut cost (and check other pillars) → Trusted Advisor
  • Attribute cost to teams/projects → Cost allocation tags
  • Combine accounts + share discounts → Organizations consolidated billing

The tools

Tool What it's for Trigger words
Cost Explorer Visualize & analyze past cost/usage, spot trends, forecast, and get RI/Savings Plan recommendations "analyze", "visualize", "trend", "where did spend go", "forecast"
AWS Budgets Set cost/usage thresholds and get alerts (on actual or forecasted spend) via email/SNS; can trigger budget actions "alert when spend exceeds", "notify", "budget", "forecasted to exceed"
Cost and Usage Report (CUR) The most detailed line-item billing data, delivered to S3, queried with Athena/Redshift/QuickSight "most granular", "detailed line items", "custom analysis", "hourly/resource-level data"
Trusted Advisor Automated checks & recommendations across cost, performance, security, fault tolerance, service limits "recommendations", "idle/underutilized resources", "best practices", "service limits"
Cost allocation tags Break down cost by tag (team, project, environment) in Cost Explorer/CUR "break down cost by department/project", "chargeback"
Compute Optimizer Right-sizing recommendations from utilization (EC2/ASG/EBS/Lambda) "right-size", "over/under-provisioned"

Key disambiguations the exam relies on:

  • Cost Explorer analyzes; Budgets alerts. "Show me the trend" → Cost Explorer. "Email me when we cross \$5,000" → Budgets.
  • Budgets vs Cost Explorer for forecasting: both forecast, but Budgets is the one that proactively alerts on a forecasted breach.
  • CUR is raw data, not a dashboard. When the ask is "most granular / resource- and hour-level data for our own analysis pipeline" → CUR (to S3 → Athena/QuickSight).
  • Trusted Advisor gives recommendations, not spend analytics — and the full set of checks requires Business or Enterprise Support (the free tier has a limited subset).

Tagging and consolidated billing

  • Cost allocation tags — activate user-defined (and AWS-generated) tags in the Billing console, then filter/group cost by them in Cost Explorer or the CUR. This is how you do chargeback/showback — "how much did the Marketing project cost this month?"
  • AWS Organizations consolidated billing — one payer account rolls up all member accounts into a single bill. Benefits: aggregated volume/tiered pricing and shared Reserved Instance / Savings Plan discounts across accounts, plus central governance (SCPs — see IAM).

Worked example — four asks, four tools

A finance lead says: (1) "Email me automatically if this month's spend is forecast to exceed \$20,000." (2) "Show me a chart of spend by service over the last 6 months." (3) "Give my data team the most granular, resource-level billing data to load into our own analytics." (4) "What idle/underutilized resources can we remove right now?"

Which tool for each?

Answer
  1. Forecasted spend alert → AWS Budgets (it alerts on actual and forecasted breaches).
  2. Chart/analyze spend by service over time → Cost Explorer.
  3. Most granular resource-level data → Cost and Usage Report (CUR) delivered to S3, queried with Athena/QuickSight.
  4. Idle/underutilized resource recommendations → Trusted Advisor (cost-optimization checks; Compute Optimizer for right-sizing specifics).

Four different needs → four different tools. Mixing them up (e.g. "Cost Explorer to alert" or "CUR to visualize") is the classic trap.

Exam traps

  • Cost Explorer = analyze/visualize/forecast; Budgets = proactively alert on a threshold.
  • "Alert when spend exceeds / is forecast to exceed" → Budgets, always.
  • CUR = most granular line-item data to S3 — raw data for your own analysis, not a dashboard.
  • Trusted Advisor = recommendations/checks across five pillars; full checks need Business/Enterprise Support.
  • Cost allocation tags are how you attribute cost to teams/projects (chargeback).
  • Consolidated billing (Organizations) aggregates volume discounts and shares RI/Savings Plan discounts across accounts.
  • Compute Optimizer (right-sizing) vs Trusted Advisor (broader best-practice checks) — both give recommendations; pick by scope.

Practice questions

Q1. A team wants to receive an email alert whenever monthly AWS spend is forecasted to exceed a set threshold. Which tool?

  • A. AWS Cost Explorer
  • B. AWS Budgets
  • C. AWS Cost and Usage Report
  • D. AWS Trusted Advisor
Answer: B

B. AWS Budgets sets cost/usage thresholds and sends alerts on actual or forecasted spend via email/SNS — built for proactive limits. Cost Explorer (A) analyzes/forecasts but isn't primarily an alerting tool. CUR (C) is raw data. Trusted Advisor (D) gives recommendations, not budget alerts.

Q2. A data team needs the most granular, resource- and hour-level billing data to load into Amazon Athena for custom cost analysis. Which should they enable?

  • A. Cost Explorer
  • B. AWS Budgets
  • C. The AWS Cost and Usage Report (CUR)
  • D. Trusted Advisor
Answer: C

C. The CUR delivers the most detailed billing line items to S3, ideal for querying with Athena/Redshift/QuickSight. Cost Explorer (A) is a visualization tool with less granularity. Budgets (B) alerts on thresholds. Trusted Advisor (D) provides recommendations, not raw billing data.

Q3. A company needs to attribute costs to individual projects and departments for internal chargeback. What should they use?

  • A. Activate cost allocation tags and group costs by them
  • B. Create a separate AWS account per project only
  • C. Use Trusted Advisor
  • D. Enable Multi-AZ
Answer: A

A. Cost allocation tags let you tag resources by project/department and then break down cost by those tags in Cost Explorer or the CUR — the standard chargeback approach. Separate accounts (B) can help but are heavier than tagging and not required. Trusted Advisor (C) gives recommendations, not cost attribution. Multi-AZ (D) is unrelated.

Q4. An organization with many AWS accounts wants a single bill, aggregated volume pricing, and the ability to share Reserved Instance / Savings Plan discounts across accounts. What provides this?

  • A. AWS Budgets
  • B. AWS Organizations consolidated billing
  • C. Separate Cost Explorer dashboards per account
  • D. AWS Trusted Advisor
Answer: B

B. Consolidated billing under AWS Organizations produces one bill, aggregates usage for volume/tiered pricing, and shares RI/Savings Plan discounts across member accounts. Budgets (A) and Trusted Advisor (D) don't combine billing. Per-account dashboards (C) don't aggregate discounts.

Q5. A manager wants a visual breakdown and trend of AWS spending by service over the past several months, plus a forecast. Which tool is the best fit?

  • A. AWS Cost and Usage Report
  • B. AWS Cost Explorer
  • C. AWS Budgets
  • D. AWS Config
Answer: B

B. Cost Explorer visualizes and analyzes historical cost/usage with filtering, grouping, and forecasting — exactly this ask. The CUR (A) is raw data needing a query tool. Budgets (C) is for threshold alerts. AWS Config (D) tracks resource configuration, not cost.

You've reached the end of the 12 Learn topics. Consolidate everything with the Cheat Sheet, track your readiness in the Gap Tracker, and test yourself with the mock exams.

Revise version: Cost Management Tools →