examhub .cc The most efficient path to the most valuable certifications.
In this note ≈ 21 min

Billing, Budgets & Cost Management (Budgets, Cost Explorer, Pricing Calculator)

4,120 words · ≈ 21 min read

AWS billing, budgets, and cost management tools give every AWS customer a single place to estimate spend before deployment, monitor spend while workloads run, alert before limits are crossed, allocate spend to teams, and export raw line-item data for deep analysis. On the CLF-C02 exam, Task Statement 4.2 (Domain 4: Billing, Pricing, and Support, 12% weight) expects you to recognise which AWS cost management tool solves which problem — and in particular to avoid the single biggest trap: confusing AWS Pricing Calculator (future estimates) with AWS Cost Explorer (past and forecast analysis). This guide covers every cost management resource in the exam blueprint in plain English, with analogies, traps, and five FAQs.

What is AWS Billing & Cost Management?

AWS Billing & Cost Management is the umbrella name for the native AWS services that let you see, forecast, control, allocate, and optimise AWS spend. The toolbox includes the AWS Billing & Cost Management Console (the central hub), AWS Pricing Calculator, AWS Cost Explorer, AWS Budgets, AWS Cost and Usage Report (CUR), Cost Allocation Tags, AWS Cost Categories, AWS Organizations consolidated billing, AWS Billing Conductor, AWS Compute Optimizer, and the cost-related checks in AWS Trusted Advisor.

Every one of these tools serves a distinct purpose. AWS billing questions on the CLF-C02 exam almost always come down to scenario matching — "given this goal, which AWS cost management tool do I pick?" — so the goal of this page is to burn each tool's job description into your memory.

Why AWS Cost Management Matters on the CLF-C02 Exam

Community data from recent CLF-C02 exam takers shows Domain 4 carries 12% weight, with billing-budget-cost-management being the broadest tool-coverage topic in the domain. The highest-frequency trap is Cost Explorer vs Budgets vs Pricing Calculator confusion, followed by Trusted Advisor tier access gotchas and AWS Organizations consolidated billing benefits. Pricing models (On-Demand/RI/Spot/Savings Plans) belong to a separate topic (4.1) — this topic is purely about the billing and AWS cost management tools.

Core termAWS Cost Management is the official AWS service family covering AWS Cost Explorer, AWS Budgets, AWS Cost and Usage Report, AWS Billing Conductor, Cost Categories, Cost Anomaly Detection, and reservation/Savings Plans management tools. It lives alongside the AWS Billing console under the single "Billing and Cost Management" experience.

Plain-Language Explanation: AWS Billing & Cost Management

Real talk: AWS billing and the full AWS cost management toolbox feel overwhelming because there are a lot of tools with similar names. Three analogies make the whole system snap into place.

Analogy 1 — The Restaurant (Menu, Bill, Budget)

Think of AWS as a restaurant. AWS Pricing Calculator is the menu — you read it before you order to estimate what dinner will cost. AWS Cost Explorer is the itemised bill you read after the meal to see where the money went and what next month's meal might cost at the same pace. AWS Budgets is telling the waiter up-front: "ring a bell when the tab hits $500." AWS Cost and Usage Report (CUR) is demanding the full kitchen receipt showing every ingredient and how much each dish cost to produce, so your accountant can do line-by-line analysis.

If you remember this restaurant image, you will never confuse AWS Pricing Calculator (future, the menu) with AWS Cost Explorer (past and forecast, the itemised bill). This is the single most tested trap in AWS cost management on the CLF-C02 exam.

Analogy 2 — The Electricity Bill at Home

AWS cost management also mirrors how you manage a household electricity bill. AWS Pricing Calculator is the utility company's calculator that estimates your bill if you install solar panels or buy an EV — a forward-looking what-if tool. AWS Cost Explorer is the graph on last month's electricity bill that shows which appliances burned the most kWh and projects next month's usage. AWS Budgets is the smart-meter alert you set to ping your phone when daily usage spikes past $5. Cost Allocation Tags are the little stickers you put on each appliance so you can answer "how much did the fridge cost last quarter?" AWS Cost and Usage Report is the raw meter log downloaded as CSV.

Analogy 3 — The Family Phone Plan (Consolidated Billing)

AWS Organizations consolidated billing is exactly like a family phone plan. Everyone (each AWS account) uses their own line, but the invoice is paid by one family member (the payer account). Because the family has more combined lines, the carrier gives volume discounts that apply across everyone's usage — in AWS this is how Reserved Instances (RIs) and Savings Plans are shared across accounts. AWS Billing Conductor is the same family plan, but you are a reseller: you set custom per-line prices for each family member (customer) while AWS still charges you the real wholesale amount.

Hold these three images (restaurant, electricity bill, family phone plan) in your head and most AWS billing CLF-C02 questions become straightforward pattern matching.

Core Operating Principles — How AWS Cost Management Works

AWS cost management operates on four pillars: visibility, forecasting, alerting, and optimisation. AWS Billing gives you the raw invoice data. AWS Cost Explorer adds visibility and forecasting on top. AWS Budgets adds alerting. AWS Compute Optimizer and AWS Trusted Advisor add optimisation recommendations. Cost Allocation Tags and Cost Categories are the tagging/grouping layer that makes the whole stack meaningful for large accounts.

The Cost Management Lifecycle

  1. Estimate — Before you deploy, use AWS Pricing Calculator to model expected cost.
  2. Deploy — Run your workloads on AWS; every resource usage is metered.
  3. Monitor — Use the AWS Billing & Cost Management Console and AWS Cost Explorer to see actuals.
  4. Alert — Configure AWS Budgets so you learn about overruns fast (not on the next invoice).
  5. Allocate — Apply Cost Allocation Tags and Cost Categories so spend ties back to teams and projects.
  6. Optimise — Act on AWS Compute Optimizer and AWS Trusted Advisor cost recommendations; adopt RIs/Savings Plans where the data justifies it.
  7. Report — Deliver CUR into Amazon S3 for BI tools (Amazon QuickSight, Athena) to build custom dashboards.

Where All AWS Cost Management Tools Live

All AWS cost management tools are reached from the AWS Billing & Cost Management Console in the AWS Management Console. Some tools (Cost Explorer, Budgets, CUR, Billing Conductor) are API-accessible too. AWS Organizations, when enabled, layers consolidated billing on top of this console for the whole organisation.

AWS Billing & Cost Management Console — The Central Hub

The AWS Billing & Cost Management Console is the single entry point. From one pane of glass you can see your current month-to-date spend, open invoices, payment methods, tax settings, credits, and — via the left navigation — drill into Cost Explorer, Budgets, Pricing Calculator, CUR, Billing Conductor, Cost Anomaly Detection, Savings Plans, and Reserved Instances reporting.

Key Features of the AWS Billing Console

  • Bills page — monthly invoice PDF, line items by service.
  • Payments — payment methods, payment history, invoice settings.
  • Credits — AWS promotional credits and where they apply.
  • Tax settings — VAT/GST registration per country.
  • Billing preferences — turn on free tier usage alerts, PDF invoice by email, turn on cost allocation tags.

AWS Billing console is the hub — On the CLF-C02 exam, if a question asks "where do I go to view invoices / manage payment methods / enable cost allocation tags?", the answer is the AWS Billing & Cost Management Console. Cost Explorer, Budgets, and Pricing Calculator are features you navigate to from this console — not separate products.

AWS Pricing Calculator — Estimate Before You Buy

AWS Pricing Calculator is a free, web-based tool at calculator.aws that lets you model the cost of a proposed AWS architecture before you deploy anything. No AWS account is required. You pick services (Amazon EC2, Amazon S3, Amazon RDS, AWS Lambda, and dozens more), configure them (instance type, region, storage, data transfer, pricing model), and get an itemised monthly and annual estimate that you can save, share as a URL, or export as CSV/PDF.

What AWS Pricing Calculator Is For

  • Building a budget proposal for management before migration.
  • Comparing two architectures (e.g. m5.large On-Demand vs m6i.large with a 3-year Compute Savings Plan).
  • Modelling the cost impact of a new region.
  • Producing a shareable estimate link for stakeholders.

What AWS Pricing Calculator Is NOT For

  • It does not show your actual AWS bill.
  • It does not look at your current usage.
  • It does not replace AWS Cost Explorer for historical analysis.
  • It does not enforce spend — it only estimates.

Pricing Calculator vs Cost ExplorerThis is the #1 CLF-C02 trap in AWS cost management. AWS Pricing Calculator estimates future costs before deployment (no account, no actual usage). AWS Cost Explorer visualises past and forecast spend of an actual AWS account. If a question says "estimate cost before migration" → Pricing Calculator. If it says "analyse last 12 months of spend" or "forecast next 12 months" → Cost Explorer. Watch for the word "estimate" + "before" vs "analyse" + "past/forecast".

AWS Cost Explorer — Visualise Past Spend and Forecast the Future

AWS Cost Explorer is the visualisation and forecasting engine for the AWS cost management stack. It provides a default dashboard plus a flexible report builder with filters (service, region, usage type, linked account, tag, purchase option) and group-by dimensions. AWS Cost Explorer data is updated at least once every 24 hours.

AWS Cost Explorer Capabilities

  • View historical spend for the past 12 months (with 13-month rolling window in the UI; 38 months via API if enabled).
  • Forecast future spend up to 12 months ahead based on historical patterns.
  • Break down cost by service, linked account, Availability Zone, instance type, tag, Cost Category, purchase option, etc.
  • Daily, monthly, and hourly granularity (hourly granularity is a paid feature opt-in).
  • Saved reports and custom dashboards.
  • Reserved Instance and Savings Plans utilisation/coverage reports built in.
  • Right-sizing recommendations powered by AWS Compute Optimizer.

When to Reach for AWS Cost Explorer on the Exam

If a question asks to analyse, visualise, break down, group, identify top-spending services, or forecast spend for an existing AWS account, AWS Cost Explorer is the answer. It is the only native AWS tool that shows past usage in a graphical dashboard without needing to export raw data.

Turn on Cost Explorer on day one — AWS Cost Explorer is free to use in the AWS console but must be explicitly enabled in the Billing preferences. Once enabled, it backfills historical data and starts populating automatically. Best practice: enable AWS Cost Explorer on the first day of your AWS account so that by the time you need to analyse spend, you already have several months of history.

AWS Budgets — Alerts Before You Overspend

AWS Budgets lets you define spend, usage, Reserved Instance, and Savings Plans thresholds and receive alerts via Amazon SNS or email when actual or forecasted metrics breach those thresholds. You can set budgets at the account level, member account level, or across an AWS Organizations organisation (from the payer account).

The Six AWS Budgets Types

  1. Cost budgets — alert when total cost hits a dollar threshold.
  2. Usage budgets — alert when usage metrics (GB-hours, request count, etc.) hit a threshold.
  3. Reservation (RI) utilization budgets — alert when RI utilization drops below a threshold (e.g. <80%).
  4. Reservation (RI) coverage budgets — alert when RI coverage of eligible usage falls below a threshold.
  5. Savings Plans utilization budgets — same as RI utilization but for Savings Plans commitment.
  6. Savings Plans coverage budgets — same as RI coverage but for Savings Plans.

AWS Budgets Actions

AWS Budgets also supports budget actions, which can automatically apply an IAM policy, attach an SCP, or stop EC2/RDS instances when a threshold is breached. This is the only AWS billing / AWS cost management feature that can take action beyond alerting.

AWS Budgets alert, they do not auto-stop spend by default — By default, AWS Budgets only sends an alert when a threshold is crossed. It does not automatically stop resources or freeze spend. You can opt-in to Budget Actions to attach an SCP, apply a restrictive IAM policy, or stop EC2/RDS instances, but this requires explicit configuration. Exam answers that say "AWS Budgets automatically stops spending when the limit is hit" are wrong unless Budget Actions are explicitly configured.

AWS Budgets vs AWS Cost Explorer — The Distinction

Question AWS Cost Explorer AWS Budgets
Shows history & forecast? Yes No
Sends alerts? No Yes
Graphical dashboard? Yes No (alert-centric)
Takes automated action? No Yes (Budget Actions)
Covers RI/SP utilization metrics? Yes (reports) Yes (as budget types)

AWS Cost and Usage Report (CUR) — Raw Line-Item Data for BI

AWS Cost and Usage Report (CUR) is the most detailed AWS billing data available. It exports every individual line item — for every hour of every resource — to an Amazon S3 bucket as compressed CSV or Parquet files. CUR data is the same source that powers Cost Explorer but is delivered raw for custom analytics.

CUR Features

  • Up to hourly granularity per resource.
  • Delivered to Amazon S3 at least once per day.
  • Can be queried directly with Amazon Athena or loaded into Amazon Redshift, Amazon QuickSight, or any third-party BI tool.
  • Includes tagging columns so every Cost Allocation Tag becomes a queryable dimension.
  • Includes Reserved Instance and Savings Plans attribution columns.

CUR vs Cost Explorer — memorise the splitCUR = raw hourly line items, delivered to S3, for BI tools to consume. AWS Cost Explorer = AWS-managed dashboard, no S3 export needed. When the CLF-C02 scenario says "detailed line-item data for custom BI pipeline" or "query billing data with Athena" → CUR. When it says "interactive graph in the AWS console" → Cost Explorer.

Cost Allocation Tags — Who Spent What

Cost Allocation Tags are the mechanism that makes AWS billing meaningful for multi-team, multi-project organisations. Tags are key-value labels you attach to resources; by activating a tag in the AWS Billing Console, that tag becomes a cost allocation dimension that surfaces in Cost Explorer, Budgets, and CUR.

Two Kinds of Cost Allocation Tags

  1. User-defined tags — tags you create (e.g. CostCenter=Marketing, Project=MobileApp, Environment=Prod). You must activate each tag in the Billing console before it appears in Cost Explorer/CUR.
  2. AWS-generated tags — tags AWS adds automatically, prefixed with aws: (e.g. aws:createdBy). Useful for default attribution.

Best Practices for Cost Allocation Tags

  • Enforce a tagging standard at account creation time via AWS Organizations tag policies.
  • Activate tags in Billing preferences — tags only become cost dimensions after activation.
  • Use Cost Categories to group many tags/accounts into a single reporting bucket.
  • Tag data begins appearing in AWS cost management tools 24 hours after activation.

AWS Cost Categories — Higher-Level Grouping

AWS Cost Categories let you define rules (based on linked account, service, region, usage type, tag) that group spend into custom buckets such as Team:Platform, BusinessUnit:EMEA, or App:CustomerPortal. Categories show up as native dimensions in AWS Cost Explorer, AWS Budgets, and CUR — so you get an attribution scheme that survives tag inconsistencies and multi-account sprawl.

AWS Organizations Consolidated Billing — One Invoice, Shared Discounts

AWS Organizations consolidated billing is the feature that merges the bills of all AWS accounts under a single organisation into one invoice paid by the payer (management) account. Member accounts still operate independently; only billing is centralised.

Three Big Consolidated Billing Benefits

  1. One invoice — finance team pays one bill for the whole organisation.
  2. Volume discounts aggregate — usage-tiered discount pricing (e.g. S3 storage tiered rates, data transfer tiered rates) is calculated on the combined usage of all accounts, unlocking lower per-unit prices.
  3. RI and Savings Plans sharing — Reserved Instances and Savings Plans purchased in any account can apply to eligible usage in any other account in the organisation (unless RI sharing is explicitly disabled).

Consolidated Billing is Free

AWS Organizations and consolidated billing have no additional charge. You are billed only for the underlying resource usage.

Consolidated billing shares RI/SP across accounts by default — With AWS Organizations consolidated billing, Reserved Instances and Savings Plans purchased in one member account can apply to matching usage in any other account in the organisation by default. This is a heavily tested CLF-C02 scenario. To disable sharing on a per-account basis, the payer must turn off RI/SP sharing for that account in the Billing preferences.

AWS Billing Conductor — Custom Billing for Resellers

AWS Billing Conductor is for AWS partners, resellers, and internal chargeback teams that need to produce custom billing views for downstream customers or business units. You define pricing rules (markups, markdowns, custom line items) on top of the AWS consolidated bill to generate a "proforma" view for each grouped unit — while AWS still charges you the real wholesale rate.

When AWS Billing Conductor is the Answer

  • A managed service provider rebills AWS to their end customers at a markup.
  • An enterprise internal team wants department-specific chargeback with custom service pricing.
  • A holding company wants each subsidiary to see a bill calculated with their own negotiated internal rates.

AWS Compute Optimizer — Right-Size with ML

AWS Compute Optimizer analyses Amazon CloudWatch metrics from EC2 instances, EC2 Auto Scaling groups, Amazon EBS volumes, AWS Lambda functions, and Amazon ECS services on AWS Fargate, then uses machine learning to recommend right-sized configurations that balance cost and performance. Recommendations are free and surface in the Compute Optimizer console, in AWS Cost Explorer's right-sizing panel, and in the AWS Trusted Advisor cost checks for supported plans.

Common Compute Optimizer Recommendation Types

  • Downsize an over-provisioned EC2 instance.
  • Switch an instance family to a newer generation (e.g. m5 → m6i or Graviton m7g) for the same workload at lower cost.
  • Reduce Lambda memory allocation where CPU headroom exists.
  • Identify under-utilised EBS volumes.

AWS Trusted Advisor — Cost Optimisation Checks

AWS Trusted Advisor provides automated checks across five pillars: cost optimisation, performance, security, fault tolerance, and service limits. For AWS cost management, the cost optimisation pillar flags items like idle load balancers, under-utilised EC2 instances, unassociated Elastic IPs, idle RDS instances, and low-utilisation Amazon Redshift clusters.

Trusted Advisor Tier Access

  • Basic Support and Developer Support plans get only the 6 core Trusted Advisor checks (security and service limit basics).
  • Business, Enterprise On-Ramp, and Enterprise plans get the full Trusted Advisor check suite, including the full cost optimisation pillar.

Trusted Advisor cost checks require Business+ support — On the CLF-C02 exam, a very common distractor is answering "use AWS Trusted Advisor to find idle EC2 instances" for a customer on the Basic or Developer support plan. Those plans only include 6 core checks — the cost optimisation checks (idle resources, low-utilisation instances) require Business, Enterprise On-Ramp, or Enterprise support. Upgrading the support plan is part of the answer.

AWS Cost Anomaly Detection — ML-Driven Surprises

AWS Cost Anomaly Detection is a managed, machine-learning-based feature inside AWS Cost Management that monitors your spend patterns and alerts (via SNS or email) when it detects unusual cost spikes. It is free to use, opt-in, and works on services, linked accounts, Cost Categories, or Cost Allocation Tag values as "monitors." It is separate from AWS Budgets (which alerts on thresholds you set manually); Cost Anomaly Detection alerts on patterns it learns.

Side-by-Side: AWS Cost Management Tools at a Glance

AWS cost management tool Time orientation Primary purpose Who uses it
AWS Pricing Calculator Future (pre-deploy) Estimate architecture cost before you buy Architects, sales, finance
AWS Cost Explorer Past + 12-month forecast Visualise and forecast spend Finance, engineering leads
AWS Budgets Threshold-based alerting Alert before overspend FinOps, account owners
AWS Cost & Usage Report (CUR) Raw historical Export raw line items to S3 Data teams, BI engineers
Cost Allocation Tags Cross-cutting Attribute cost to teams/projects All of the above
AWS Cost Categories Cross-cutting Group cost by custom rules FinOps
AWS Organizations consolidated billing Real-time Merge bills, share RI/SP Finance (multi-account)
AWS Billing Conductor Real-time Custom reseller/chargeback pricing Resellers, MSPs
AWS Compute Optimizer Continuous Right-sizing recommendations Engineering
AWS Trusted Advisor (cost) Continuous Idle-resource alerts Ops (Business+ plan)
AWS Cost Anomaly Detection Continuous ML anomaly alerts FinOps

Key Numbers and Must-Memorize Facts

  • AWS Cost Explorer stores up to 13 months of history in the UI and can forecast up to 12 months ahead; API access can extend to 38 months with opt-in.
  • AWS Budgets: two free action-enabled budgets per account, then $0.10 per action-enabled budget per day; cost and usage budgets themselves have a small-per-budget-per-day charge after the first two.
  • AWS Cost and Usage Report (CUR) delivers to an S3 bucket you own, at least once per day, with hourly granularity available.
  • AWS Organizations consolidated billing is free; RI/SP sharing is on by default.
  • AWS Pricing Calculator is free and requires no AWS account.
  • Cost Allocation Tags take roughly 24 hours after activation to appear in AWS cost management tools.
  • AWS Trusted Advisor cost checks are Business+ only for the full set; Basic/Developer only get 6 core checks.
  • AWS Compute Optimizer is free to use.
  • Cost Anomaly Detection is free to use (notifications via SNS/email — SNS charges standard rates).

Common Exam Traps — Spot Them Fast

Trap 1 — Pricing Calculator vs Cost Explorer

Covered above. The single most common AWS billing trap. Keyword cues: "before deployment" → Pricing Calculator. "past 12 months", "forecast", "visualise" → Cost Explorer.

Trap 2 — AWS Budgets "auto-stops" spending

AWS Budgets alerts by default. Automated stopping requires explicitly configuring Budget Actions. Any answer implying AWS Budgets natively freezes all spend is wrong.

Trap 3 — CUR vs Cost Explorer

CUR = raw line-item CSV/Parquet files in S3 for BI tools. Cost Explorer = dashboard in AWS console. Scenarios mentioning "Athena", "QuickSight", "custom BI pipeline", "hourly line items" → CUR.

Trap 4 — Consolidated billing and RI/SP sharing

Consolidated billing in AWS Organizations shares RI and Savings Plans discounts across all member accounts by default. Do not confuse this with SCP (Service Control Policies), which govern permissions, not billing.

Trap 5 — Trusted Advisor cost checks limited by support plan

Only Business, Enterprise On-Ramp, and Enterprise support tiers unlock the full Trusted Advisor cost optimisation pillar. Basic and Developer plans see only 6 core checks.

Trap 6 — AWS Pricing Calculator does not need an AWS account

Every other AWS cost management tool requires an AWS account. AWS Pricing Calculator does not — anyone can open calculator.aws and build an estimate. This appears in scenario questions where a prospect without an AWS account needs to estimate cost.

Trap 7 — AWS Cost Explorer is not enabled by default

AWS Cost Explorer must be explicitly enabled in billing preferences on first use. It backfills historical data afterwards.

AWS Billing Scope vs Pricing Models (Task 4.1) vs Support Plans (Task 4.3)

CLF-C02 Domain 4 is split into three task statements:

  • 4.1 Pricing Models — On-Demand, Reserved Instances, Savings Plans, Spot. Not AWS cost management tools.
  • 4.2 Billing, Budgets & Cost Management (THIS TOPIC) — Cost Explorer, Budgets, Pricing Calculator, CUR, cost allocation, Organizations consolidated billing, Billing Conductor, Compute Optimizer.
  • 4.3 Technical Resources & Support — AWS Support plans, Trusted Advisor tier access rules, TAM, AWS IQ, Marketplace. Trusted Advisor itself is a shared tool but its tier access rules live here.

Most AWS billing questions stay in their lane; a few deliberately cross the boundary (e.g. "Trusted Advisor cost checks require which support plan?"). Train yourself to recognise which task a scenario belongs to.

Practice Question Patterns — What AWS Cost Management Questions Look Like

  1. "A company wants to estimate monthly cost of running three m6i.large EC2 instances and an RDS db.r6g.xlarge before migrating. Which AWS service should they use?" → AWS Pricing Calculator.
  2. "A FinOps team needs to see spend trends over the past 12 months broken down by linked account and service, plus a forecast for next quarter." → AWS Cost Explorer.
  3. "The CTO wants an email when monthly AWS spend is forecasted to exceed $10,000." → AWS Budgets (cost budget with forecasted threshold).
  4. "The data team wants hourly line-item billing data delivered to an S3 bucket for Athena analysis." → AWS Cost and Usage Report (CUR).
  5. "A managed service provider needs to apply custom markup pricing per customer and produce a per-customer billing view." → AWS Billing Conductor.
  6. "A finance team wants to see spend grouped by business unit even though the accounts span multiple teams." → AWS Cost Categories (plus Cost Allocation Tags).
  7. "A company with 30 AWS accounts wants a single invoice and to share Reserved Instance discounts across accounts." → AWS Organizations consolidated billing.
  8. "An engineering team wants rightsizing recommendations for EC2 and Lambda." → AWS Compute Optimizer.
  9. "An ops team on the Basic Support plan wants AWS Trusted Advisor to flag idle load balancers." → Upgrade to Business, Enterprise On-Ramp, or Enterprise support.

FAQ — AWS Billing, Budgets & Cost Management Top 5 Questions

Q1: What is the difference between AWS Pricing Calculator and AWS Cost Explorer?

AWS Pricing Calculator estimates the cost of a proposed architecture before you deploy anything, requires no AWS account, and is used for planning and budgeting. AWS Cost Explorer visualises and forecasts the spend of an existing AWS account using historical billing data (up to 13 months in the UI) and requires Cost Explorer to be enabled in the account. If a CLF-C02 scenario says "before migration" or "prospective customer", Pricing Calculator. If it says "past spend", "forecast", or "break down existing bill", Cost Explorer.

Q2: Does AWS Budgets automatically stop AWS services when I exceed my budget?

No — not by default. AWS Budgets sends alerts via Amazon SNS or email when actual or forecasted cost/usage crosses a threshold. To enforce action, you must configure AWS Budgets Actions, which can attach restrictive IAM policies, apply SCPs, or stop EC2/RDS instances. Even then, auto-stop is scoped to the resources you explicitly include. Treat AWS Budgets as an alerting and governance tool, not an automatic kill switch.

Q3: Do I pay extra for AWS Organizations consolidated billing?

No. AWS Organizations and consolidated billing have no additional charge — you pay only for the underlying AWS resource usage. Consolidated billing is actually cost-saving because tiered volume discounts (e.g. S3 storage tiers) are calculated on your combined organisation-wide usage, and Reserved Instances plus Savings Plans are shared across member accounts by default.

Q4: When should I use AWS Cost and Usage Report (CUR) instead of AWS Cost Explorer?

Use AWS Cost Explorer when the built-in dashboard, filters, and forecast are enough and you want zero setup. Use CUR when you need raw hourly line items delivered to Amazon S3 for custom analytics pipelines — for example, querying with Amazon Athena, loading into Amazon Redshift, or powering a QuickSight dashboard with custom joins to your own systems. CUR is the source-of-truth raw data; Cost Explorer is the managed dashboard.

Q5: How do Cost Allocation Tags relate to AWS Cost Categories?

Cost Allocation Tags are key-value labels applied at the resource level (per EC2 instance, per S3 bucket) and activated in Billing preferences to become cost dimensions. AWS Cost Categories are rule-based groupings that live above tags — a category rule can combine tags, accounts, services, and regions into a single named bucket (e.g. Team:Platform). Use tags for granular per-resource attribution; use Cost Categories to create stable reporting groups that survive tag inconsistency and to build hierarchical views of organisational spend.

Q6: Does AWS Pricing Calculator include Reserved Instance and Savings Plans discounts?

Yes. When configuring a service in AWS Pricing Calculator, you can select On-Demand, Reserved Instance (1-year or 3-year, no/partial/all upfront), or Savings Plans (Compute or EC2 Instance) pricing. This lets you model the cost impact of commitment discounts before you purchase. However, Pricing Calculator estimates the list price under each model — it does not replace Cost Explorer's Reserved Instance/Savings Plans utilization and coverage reports, which analyse actual usage against commitments you already own.

Further Reading

  • AWS Pricing Models (Task 4.1) — On-Demand, Reserved Instances, Savings Plans, Spot Instances deep dive.
  • Cloud Economics (Task 1.4) — CapEx vs OpEx, TCO, rightsizing economics.
  • Technical Resources & Support (Task 4.3) — AWS Support plan tiers, full Trusted Advisor tier access rules, TAM, AWS IQ.

Master AWS billing and the AWS cost management toolbox at this topic's depth and you have locked in roughly one-third of Domain 4's question budget on the CLF-C02 exam — and built the foundation for every FinOps practice you will touch on the job.

Official sources