Billing, Pricing, and Support
Cost Management, Billing, and Organizations
CoreChoose the right AWS resource to estimate a planned workload, analyze actual spend, watch thresholds, export detailed records, allocate cost, or consolidate billing.
Aligned to the current CLF-C02 exam guide, verified August 15, 2026.
Why this matters
Cost questions often present several legitimate AWS tools. The deciding clue is whether the company is planning, analyzing, alerting, exporting, allocating, or governing accounts.
Must Know
- AWS Pricing Calculator estimates the cost of a proposed architecture or change before deployment using stated assumptions.
- AWS Cost Explorer visualizes and filters historical cost and usage and can forecast supported future periods from history.
- AWS Budgets compares actual or forecast cost, usage, or commitment metrics with thresholds and sends alerts or performs supported actions.
- AWS Cost and Usage Reports provide granular billing line items for detailed analysis and allocation.
- Cost allocation tags label resources for billing analysis after the tags are activated for cost allocation; AWS-generated and user-defined tags have different origins.
- AWS Organizations consolidated billing combines charges across member accounts and can share eligible volume discounts and commitment benefits while accounts remain separate.
Compare and Distinguish
- Pricing Calculator vs Cost Explorer: Calculator models a proposal; Cost Explorer studies costs produced by actual usage.
- Cost Explorer vs Budgets: Cost Explorer investigates trends and drivers; Budgets watches defined thresholds and alerts.
- Cost Explorer vs Cost and Usage Reports: Cost Explorer is an interactive analysis experience; reports supply detailed exported line items for custom analysis.
- Organizations vs cost allocation tags: Organizations establishes account structure and consolidated billing; tags attribute costs to projects, teams, or other dimensions.
- Service control policies vs consolidated billing: SCPs are permission guardrails; consolidated billing is a financial capability.
Scenario examples
- Scenario: A team wants a monthly estimate for a design that has not been deployed. Think: AWS Pricing Calculator.
- Scenario: Finance wants to understand which service drove last month’s increase. Think: AWS Cost Explorer.
- Scenario: A manager wants an email before forecast spend crosses a limit. Think: AWS Budgets.
- Scenario: An analyst needs granular cost line items labeled by project. Think: Activate cost allocation tags and use AWS Cost and Usage Reports.
Exam traps
- Pricing Calculator results are estimates, not a guarantee of the future bill.
- Budgets can notify and take supported actions, but a budget does not replace detailed cost analysis.
- Attaching an ordinary resource tag does not retroactively label past billing data.
- Consolidated billing does not give administrators in one member account automatic access to another member account.
- SCPs restrict maximum available permissions; they do not grant access or allocate costs.
Key takeaways
- Plan: Pricing Calculator. Analyze: Cost Explorer. Alert: Budgets.
- Export detail: Cost and Usage Reports. Attribute: cost allocation tags.
- Group accounts and bills: AWS Organizations.
How it works
- Pricing Calculator multiplies usage assumptions by applicable pricing data to produce an estimate.
- Cost Explorer processes billing data into filterable views and forecasts.
- Budgets evaluates actual or forecast values against configured thresholds.
- Cost and Usage Reports deliver detailed records to Amazon S3 for downstream analysis.
- Organizations aggregates billing across linked accounts and applies eligible sharing rules.
When to use it
- Use Pricing Calculator during planning or migration business-case work.
- Use Cost Explorer after usage exists and the question concerns trends, drivers, or forecasts.
- Use Budgets when stakeholders need threshold notifications or supported budget actions.
- Use detailed reports and tags for chargeback, showback, or custom cost analysis.
- Use Organizations for multi-account management and consolidated billing.
Security and governance implications
- Apply least privilege to billing and cost-management access; financial visibility can be sensitive.
- Maintain account isolation and governance even when billing is consolidated.
Troubleshooting signals
- If a tag is missing from cost views, verify that the resource supports tagging, the tag existed during the usage period, and it was activated as a cost allocation tag.
- If an expected discount is absent, check eligibility, purchase attributes, organizational sharing settings, and the time required for billing data to update.
More detail
- Billing information is available through AWS Billing and Cost Management. Access to billing data is controlled; it should not be treated as automatically visible to every IAM identity.
- User-defined cost allocation tags originate from customer-applied resource tags. AWS-generated tags are created by AWS. Both must be activated where required before appearing as cost allocation dimensions.
- A management account receives the consolidated bill for an organization. Member accounts remain operationally distinct, and governance controls can be applied through organizational structures.
- AWS Cost and Usage Reports remain explicit CLF-C02 scope even as AWS adds newer export experiences. Teach the guide-listed detailed-reporting purpose.
Ready for the quiz?
- Which tool fits a cost question before any resources exist?
- What is the difference between analyzing a trend and monitoring a threshold?
- Why would a company use a Cost and Usage Report instead of only Cost Explorer?
- What does consolidated billing change, and what does it leave separate?
Related objectives
- D4.2