AWS Cloud Practitioner Study Notes · Part 37
AWS Cloud Financial Management: Cost Explorer, Budgets, and Optimization
AWS Cloud Practitioner study notes mapping Pricing Calculator, Cost Explorer, Budgets, anomaly detection, CUR, tags, Compute Optimizer, and billing.
Cloud financial management is the ongoing practice of planning, understanding, controlling, allocating, and optimising cloud costs. It starts before deployment with a cost estimate and continues after deployment with reports, budgets, anomaly alerts, tags, rightsizing, and pricing commitments.
This is Part 37 of the AWS Cloud Practitioner Study Notes. Part 9 introduced AWS pricing and billing, while Part 36 explained TCO, AWS Pricing Calculator, and Migration Evaluator.
The cloud financial management lifecycle
Plan and compare
│
▼
Deploy with account and tagging structure
│
▼
Analyse actual spending
│
▼
Set budgets and alerts
│
▼
Detect unusual costs
│
▼
Allocate costs to teams and applications
│
▼
Rightsize and optimiseThe tools are easier to remember when grouped by the question they answer.
1. Plan and compare costs
AWS Pricing Calculator
Use AWS Pricing Calculator when you have a proposed AWS architecture and want to estimate its cost before deployment or before changing an existing workload.
Example inputs include:
- EC2 instance count and types
- EBS storage
- RDS or Aurora capacity
- S3 storage and requests
- Elastic Load Balancing
- Data transfer
- Expected hours, requests, and usage patterns
- Payment options and eligible commitments
Proposed architecture
│
▼
Pricing Calculator
│
▼
Estimated AWS workload costExam shortcut: “Estimate the monthly cost of AWS resources before creating them” → AWS Pricing Calculator.
AWS Migration Evaluator
Use AWS Migration Evaluator when an organisation has an existing on-premises or data-centre environment and wants a data-driven business case for moving workloads to AWS. It can use server inventory and utilisation information such as CPU, memory, storage, licensing, and current infrastructure costs.
Migration Evaluator was formerly known as TSO Logic. It focuses on migration assessment and projected cost or savings scenarios rather than simply pricing a new AWS design.
Exam shortcut: “Compare the existing data centre with AWS and estimate migration savings” → AWS Migration Evaluator.
2. Analyse actual costs with Cost Explorer
AWS Cost Explorer helps you visualise, filter, group, and forecast existing AWS cost and usage data. It is the tool for understanding what has already happened and identifying trends.
Questions Cost Explorer can help answer include:
- Why did the bill increase last month?
- Which AWS service costs the most?
- Which Region or member account is generating the spend?
- How much did the development environment cost?
- What is the forecasted cost for the current month?
You can group or filter by dimensions such as service, account, Region, Availability Zone, usage type, instance type, cost allocation tags, and cost categories.
Example:
Monthly spend increased from $500 to $900
│
▼
Cost Explorer groups by service
│
├── EC2: $350
├── RDS: $180
├── Data transfer: $300
└── S3: $70Exam shortcut: visualise historical spending, identify trends, or forecast costs → AWS Cost Explorer.
3. Control spending with AWS Budgets
AWS Budgets lets you define cost or usage targets and receive alerts when actual or forecasted values exceed configured thresholds.
Monthly budget: $1,000
Alert at 50% → $500
Alert at 80% → $800
Alert at 100% → $1,000Budget types can track:
- Cost in currency
- Usage such as EC2 hours
- Reserved Instance utilisation and coverage
- Savings Plans utilisation and coverage
You can filter budgets by services, accounts, Regions, tags, cost categories, usage types, and other supported dimensions. AWS Budgets can also support configured budget actions, such as applying a policy or targeting supported resources, subject to permissions and configuration.
An AWS Budget is not a universal hard spending cap. Reaching a threshold normally produces an alert; resources do not automatically stop unless an explicit, supported budget action has been configured.
Exam shortcut: alert when actual or forecasted spending reaches a threshold → AWS Budgets.
4. Detect unusual spending with Cost Anomaly Detection
AWS Cost Anomaly Detection uses machine-learning-based analysis to identify spending patterns that are unusual for the monitored account, service, cost allocation tag, or cost category.
The difference from a budget is the comparison method:
AWS Budgets
→ Did cost exceed my predefined target?
Cost Anomaly Detection
→ Is spending behaving unusually compared with the normal pattern?For example, an account may normally spend $100 per weekday and $40 per weekend day. A sudden $900 daily charge can be identified as an anomaly even if the monthly budget has not yet been exceeded.
Notifications can be configured through supported alert subscriptions such as email or Amazon SNS.
Exam shortcut: detect unexpected or unusual cost spikes → AWS Cost Anomaly Detection.
5. Detailed reporting with CUR and Data Exports
The AWS Cost and Usage Report (CUR) provides detailed billing and usage data for custom analysis. It is useful when Cost Explorer’s charts are not detailed enough for finance, chargeback, showback, data warehousing, or custom dashboards.
A common reporting flow is:
AWS billing data
│
▼
CUR or AWS Data Exports
│
▼
Amazon S3
│
├── Athena queries
├── QuickSight dashboards
└── Custom finance reportingAWS Data Exports is the newer configurable export capability. It can create recurring exports, select columns, filter rows, and export detailed billing and cost-management datasets to Amazon S3. CUR 2.0 is the current recommended detailed cost and usage export in the Data Exports experience, while legacy CUR terminology still appears in many exam materials and existing architectures.
Exam shortcut: “most detailed billing and usage data for custom analysis” → Cost and Usage Report (CUR) or the current AWS Data Exports equivalent.
6. Allocate costs with tags
Cost allocation tags connect AWS spending to business meaning. Useful tag examples include:
Environment = Production
Project = Checkout
Department = Finance
Owner = Platform-TeamAfter the relevant user-defined tags are activated as cost allocation tags, they can be used in cost analysis and exports. Consistent tagging enables:
- Showback: show teams what they consumed
- Chargeback: allocate or internally bill teams for consumption
- Project-level reporting
- Production versus development comparisons
- Ownership and accountability
Tags are only useful when resources are tagged consistently. Establish naming rules, automate required tags, and monitor unallocated spend.
7. Group business costs with Cost Categories
AWS Cost Categories create business-level groupings using rules. Unlike a resource tag, a cost category can combine accounts, services, Regions, tags, and other billing dimensions into a broader reporting model.
Production
= Account A
+ Account B
+ Environment=Production
Development
= Account C
+ Environment=DevelopmentCost categories can appear as dimensions in Cost Explorer, AWS Budgets, CUR or Data Exports, and Cost Anomaly Detection. They are useful when finance needs views such as business unit, product line, environment, or customer segment rather than raw resource tags.
Cost allocation tags → label resources
Cost Categories → group billing line items into business views8. Optimise with Compute Optimizer
AWS Compute Optimizer analyses resource configuration and utilisation and provides recommendations for supported resources. For EC2, it can recommend more appropriate instance types and show estimated savings opportunities.
Example:
Current: m7i.4xlarge
Average CPU: 5%
│
▼
Compute Optimizer recommendation
│
▼
Consider a smaller instanceRightsizing means matching capacity to actual workload needs. Other examples include stopping idle resources, adjusting an over-sized RDS instance, removing unused EBS volumes, and reviewing unattached addresses or stale snapshots.
Recommendations are inputs to a decision, not automatic permission to resize production. Check memory, network, I/O, latency, burst patterns, licensing, and application limits before applying them.
Exam shortcut: “recommend the optimal resource configuration based on utilisation” → AWS Compute Optimizer.
9. Reduce predictable compute costs
Savings Plans, Reserved Instances, and Spot Instances are pricing or purchasing options rather than analysis tools.
Savings Plans
Savings Plans provide discounted rates in exchange for a commitment to a consistent amount of eligible usage, usually measured in dollars per hour, for a one- or three-year term. They are useful for predictable compute usage when the organisation can commit to the term.
Reserved Instances
Reserved Instances provide discounted pricing for eligible services in exchange for a commitment. Depending on the service and RI type, they may also provide a capacity reservation benefit.
Spot Instances
Spot Instances use spare AWS capacity at a discount but can be interrupted. They are best for fault-tolerant, flexible workloads rather than critical stateful services that cannot tolerate interruption.
Stable predictable usage → Savings Plans or Reserved Instances
Short-term uncertain use → On-Demand
Interruptible workloads → Spot Instances10. Consolidate accounts and billing
AWS Organizations lets a company manage multiple AWS accounts centrally. With consolidated billing, the organisation receives a combined bill and can view member-account spending through the management account or configured billing roles.
Management account
├── Production account
├── Development account
├── Security account
└── Testing accountSeparate accounts provide workload isolation, security boundaries, and clearer ownership while consolidated billing provides central financial visibility. Depending on the service and billing rules, aggregated usage can also affect volume pricing and the sharing of eligible Savings Plans or Reserved Instance benefits.
The complete cost-management workflow
1. Compare existing infrastructure
→ Migration Evaluator
2. Estimate planned AWS architecture
→ AWS Pricing Calculator
3. Deploy with account and tag structure
→ Organizations, tags, Cost Categories
4. Analyse actual costs
→ Cost Explorer
5. Set thresholds and alerts
→ AWS Budgets
6. Detect unusual spending
→ Cost Anomaly Detection
7. Export detailed billing data
→ CUR / AWS Data Exports
8. Rightsize resources
→ Compute Optimizer
9. Apply suitable pricing commitments
→ Savings Plans / Reserved InstancesCommon exam questions
| Requirement | Likely answer |
|---|---|
| Estimate planned AWS service costs | AWS Pricing Calculator |
| Compare an on-premises environment with AWS | AWS Migration Evaluator |
| View historical spending and trends | AWS Cost Explorer |
| Alert when spending exceeds a fixed threshold | AWS Budgets |
| Detect an unexpected spending spike | Cost Anomaly Detection |
| Obtain detailed billing and usage data | Cost and Usage Report / Data Exports |
| Categorise costs by project or department | Cost allocation tags |
| Group costs into production, development, or business units | AWS Cost Categories |
| Get rightsizing recommendations | AWS Compute Optimizer |
| Discount predictable long-term compute usage | Savings Plans or Reserved Instances |
| Combine billing across multiple accounts | AWS Organizations consolidated billing |
Common exam traps
Cost Explorer versus AWS Budgets
Cost Explorer analyses actual cost and usage. AWS Budgets compares actual or forecasted values with a target and sends alerts or configured actions.
Budgets versus Cost Anomaly Detection
Budgets ask whether a predefined threshold was crossed. Anomaly Detection asks whether the spending pattern is unusual compared with the account’s normal behaviour.
Pricing Calculator versus Cost Explorer
Pricing Calculator estimates planned or changed AWS usage. Cost Explorer analyses actual historical AWS spending.
Pricing Calculator versus Migration Evaluator
Pricing Calculator asks what the proposed AWS resources may cost. Migration Evaluator helps assess the financial case for moving an existing environment to AWS.
Tags versus Cost Categories
Tags label resources. Cost Categories apply business rules to group billing line items and can combine multiple dimensions.
Savings Plans versus cost monitoring
Savings Plans reduce eligible usage rates through a commitment. They do not show why the bill changed; use Cost Explorer for analysis.
Memory map for CLF-C02
- Plan AWS costs → AWS Pricing Calculator
- Compare on-premises and AWS → AWS Migration Evaluator
- Analyse historical spending → AWS Cost Explorer
- Alert on a spending threshold → AWS Budgets
- Detect unusual spending → Cost Anomaly Detection
- Export detailed billing data → CUR / AWS Data Exports
- Track project or department costs → Cost allocation tags
- Create business-level groupings → Cost Categories
- Recommend rightsizing → Compute Optimizer
- Discount predictable usage → Savings Plans / Reserved Instances
- Combine account billing → AWS Organizations
Conclusion
AWS cloud financial management is a continuous lifecycle. Pricing Calculator and Migration Evaluator support planning. Cost Explorer explains actual usage. Budgets control thresholds, Cost Anomaly Detection identifies unusual behaviour, and CUR or Data Exports support detailed reporting. Tags and Cost Categories allocate costs, while Compute Optimizer and pricing commitments help reduce avoidable spend.
The core exam rule is: Pricing Calculator estimates, Cost Explorer analyses, Budgets alerts on targets, Anomaly Detection finds unusual patterns, CUR reports details, tags allocate, Cost Categories group, and Compute Optimizer recommends rightsizing.