Cloud Financial Management
Tools for tracking, forecasting, allocating, and controlling AWS spend across accounts.
AWS Budgets
Set custom cost and usage thresholds, get alerted, and optionally trigger automated actions when spend crosses the line.
- Four budget flavors: cost, usage, RI utilization/coverage, Savings Plans utilization/coverage
- Alerts fire on actual OR forecasted spend — forecasted is the one that saves you before the damage is done
- Budget actions can auto-apply an IAM policy or SCP, or stop specific EC2/RDS instances — run automatically or after manual approval
- Data refreshes up to 3x/day (8–12 hours apart) — it's a smoke alarm, not a circuit breaker; spend can run for hours before a budget notices
Exam triggers
Phrases and scenarios that point here.
- "Alert me when spending exceeds/is forecasted to exceed X" → Budgets, not Cost Explorer
- "Automatically stop resources / restrict provisioning when a threshold is hit" → budget actions
- "Notify before the bill arrives" → forecasted alert
- Proactive threshold alerting → Budgets; historical analysis → Cost Explorer
Not this service
- Analyze and visualize past spend → Cost Explorer
- Anomaly detection with ML (unexpected spikes, no threshold set) → Cost Anomaly Detection
- Itemized line-by-line billing data → Cost and Usage Report (CUR)
Use cases
- The classic student/sandbox guardrail: a $10 monthly budget with a forecasted alert at 80%, so a forgotten NAT Gateway pages you before it eats the month
- Per-team or per-project spend caps using tag or account filters — each squad's dev environment gets its own budget and its own alert
- A budget action that attaches a deny-provisioning IAM policy when a dev account hits 100% — spend freezes without anyone being awake
- RI/Savings Plans utilization budget alerting when usage drops below 80% — you already paid for the commitment, this tells you it's going idle
- Custom period budget matching a project or grant window (e.g., a 3-month migration), instead of forcing it into calendar months
Commonly confused with
Verified against AWS documentation · 2026-08-28
AWS Cost and Usage Report (CUR)
The most detailed AWS billing dataset — line-item cost and usage data delivered to an S3 bucket you own.
- Delivers granular line items (per service, per resource, per hour if enabled) as files into your S3 bucket — it's raw data, not a dashboard
- Time granularity: hourly, daily, or monthly; optionally includes resource IDs for per-resource cost attribution
- Refreshed at least once a day; initial delivery can take up to 24 hours after setup
- Integrates with Athena (query with SQL), QuickSight (visualize), and Redshift (warehouse) — Parquet format is built for the Athena path
- Tracks Reserved Instance and Savings Plans utilization at the line-item level — the data source for serious commitment analysis
Exam triggers
Phrases and scenarios that point here.
- "Most detailed" or "most granular" billing/cost data → CUR
- "Analyze costs with SQL / Athena" or "custom cost dashboards in QuickSight" → CUR in S3
- Cost data "delivered to S3" → CUR (Cost Explorer has no S3 delivery)
- Chargeback / showback per team, per resource, or per tag → CUR with resource IDs and cost allocation tags
Not this service
- Visual point-and-click cost exploration and forecasts → Cost Explorer
- Alerts when spend crosses a threshold → AWS Budgets
- Cost optimization recommendations → Trusted Advisor / Compute Optimizer
- Splitting bills across business units → AWS Billing Conductor
Use cases
- Feeding a FinOps pipeline: CUR lands in S3, Athena queries it, QuickSight dashboards it — the standard homegrown cost analytics stack
- Chargeback: tagging resources by team, then using CUR line items to bill each department for exactly what they consumed
- Auditing a surprise bill — CUR is where you find *which* resource, in *which* hour, generated the charge Cost Explorer only shows as a spike
- Verifying RI and Savings Plans coverage before renewing commitments, using actual utilization line items instead of estimates
Commonly confused with
Verified against AWS documentation · 2026-08-28
AWS Cost Explorer
Visual analysis and forecasting tool for your AWS cost and usage data.
- Views up to 13 months of historical cost and usage; forecasts up to 18 months ahead (monthly) or 3 months (daily)
- Filter and group by service, account, Region, tag, usage type — answers "what is costing me money and why"
- Includes Reserved Instance and Savings Plans recommendations, utilization, and coverage reports
- Console UI is free; the API and hourly granularity are the only paid parts
- Once enabled it can't be disabled; data refreshes at least once every 24 hours — it's analysis, not real-time monitoring
Exam triggers
Phrases and scenarios that point here.
- "Visualize", "analyze", "break down" past or current spend → Cost Explorer
- "Forecast" or "predict" future AWS costs → Cost Explorer
- "Which service/account/tag is driving the bill" → Cost Explorer with filters/grouping
- Historical spend trends over months → Cost Explorer, not the Billing dashboard
Not this service
- Alert me when spend crosses a threshold → AWS Budgets
- Most detailed line-item billing data for BI tools → Cost and Usage Report (Data Exports)
- Estimate costs *before* building anything → AWS Pricing Calculator
- Right-sizing compute based on performance metrics → AWS Compute Optimizer
Use cases
- Monday-morning bill shock triage: a $400 jump appeared on the invoice — group by service, then by usage type, and find the NAT Gateway data processing nobody noticed
- Chargeback by team: filter by cost allocation tags to show each squad exactly what their workloads cost last quarter
- Deciding whether Savings Plans are worth it: check the built-in recommendations and coverage reports before committing to 1- or 3-year terms
- Budget planning: use the 18-month forecast to give finance a defensible number instead of a guess
- Feeding a custom cost dashboard via the API when the console views aren't enough
Commonly confused with
Verified against AWS documentation · 2026-08-28
AWS Marketplace
Curated digital catalog for finding, buying, and deploying third-party software that runs on AWS — billed through your AWS bill.
- Third-party software, not AWS services — AMIs, SaaS, containers, CloudFormation-delivered products, data products, and professional services
- Charges land on your existing AWS bill — one invoice, no separate vendor procurement or payment setup
- Pricing models: free, BYOL, hourly, monthly, annual/multi-year contracts, and usage-based
- Anyone with an AWS account can buy; sellers register via the AWS Marketplace Management Portal (tax + banking info required for paid products)
- Private offers let a buyer and seller negotiate custom pricing and terms off the public listing
Exam triggers
Phrases and scenarios that point here.
- "Third-party software", "pre-configured AMI", "software vendor" → Marketplace
- "Consolidate software spend on the AWS bill" / "simplify procurement" → Marketplace
- Launch an EC2 instance with commercial software already licensed and installed → Marketplace AMI
- "Sell your own software to AWS customers" → register as a Marketplace seller
Not this service
- Pre-built internal deployment templates governed by your own org → Service Catalog
- Buying/subscribing to third-party datasets specifically → AWS Data Exchange (delivered via Marketplace)
Use cases
- Spinning up a firewall, monitoring agent, or database appliance as a ready-made AMI instead of licensing it separately and installing it yourself — think app store for your VPC
- A startup buying SaaS (e.g. monitoring or security tooling) through Marketplace so finance sees one AWS invoice instead of ten vendor contracts
- Enterprises routing software purchases through Marketplace so spend counts toward existing AWS commitment agreements
- An ISV selling their product to AWS customers using AWS's billing and disbursement rails instead of building their own
Commonly confused with
Verified against AWS documentation · 2026-08-28