Study guide

Technical reference and lesson notes

AWS Cost Management Tools: Cost Explorer, CUR, and Price List APIs

Purpose of This Lesson

This lesson explains the roles, capabilities, and selection criteria for key AWS cost management tools:

AWS Cost Explorer for interactive cost analysis and forecasting.
AWS Cost and Usage Report (CUR) for detailed billing data delivered to Amazon S3.
AWS Price List APIs for querying AWS service prices and supporting custom price-monitoring systems.

The main assessment skill is recognizing which tool fits a requirement for visualization, detailed reporting, or programmatic price lookup.

Key Concepts

Cost Explorer

Cost Explorer is a free tool for viewing charts and analyzing AWS costs. It supports:

Reviewing cost data for the previous 13 months.
Forecasting expected spending for up to 3 months into the future.
Identifying spending patterns over time.
Examining service usage statistics.
Comparing usage by Availability Zone.
Identifying which linked account is used most within an AWS Organizations environment.

Cost Explorer is primarily an interactive analysis tool. It helps explain what is happening with AWS spending and supports investigation through charts and filters.

AWS Cost and Usage Report

The AWS Cost and Usage Report, commonly called CUR, publishes billing reports to an Amazon S3 bucket. The report can break down costs by:

Hour
Day
Month
Product
Product resource
Tags

Reports can be updated up to three times per day. The AWS CUR API can be used to create, retrieve, and delete reports.

CUR is suited to detailed, exportable billing data and custom analysis outside the interactive Cost Explorer experience.

AWS Price List APIs

The AWS Price List APIs provide programmatic access to AWS service pricing. The lecture identifies two components:

Price List Service API, also called the Query API, which supports JSON queries.
AWS Price List API, also called the Bulk API, which is queried with HTML.

Price data can be used to build a custom system that checks AWS prices and sends notifications, including SMS alerts, when prices change.

Cost and Billing Tool Selection

The tools address different questions:

Requirement	Appropriate tool	Reason
Explore spending interactively with charts	Cost Explorer	Provides historical cost views, filters, usage statistics, and forecasts.
Review spending patterns over time	Cost Explorer	Designed for exploration and trend analysis.
Export detailed hourly, daily, or monthly billing data	CUR	Publishes granular cost and usage data to Amazon S3.
Analyze costs by product resource or tags	CUR	These dimensions are included in the detailed report.
Create, retrieve, or delete billing reports programmatically	AWS CUR API	Provides API operations for report management.
Query AWS service prices in JSON	Price List Service API / Query API	Supports JSON-based price queries.
Query AWS pricing through the bulk interface	AWS Price List API / Bulk API	Uses the bulk pricing interface described in the lesson.
Build a custom price-change monitoring system	Price List APIs	Pricing data can support custom checks and notifications.

Exam- or Assessment-Relevant Takeaways

Cost Explorer is the choice for interactive cost visualization, historical analysis, usage-pattern discovery, and forecasting.
Cost Explorer provides up to 13 months of historical cost data and forecasts up to 3 months ahead.
In an AWS Organizations environment, Cost Explorer can help compare usage across linked accounts.
CUR delivers detailed billing reports to Amazon S3, making it the better fit for granular exports and custom downstream analysis.
CUR supports breakdowns by time period, product, product resource, and tags.
CUR reports can be updated up to three times per day.
Use the AWS CUR API to manage CUR reports programmatically.
Use the Price List Service API / Query API for JSON pricing queries and the Bulk API for the bulk pricing interface.
Do not confuse a cost-analysis tool with a pricing-query tool: Cost Explorer analyzes incurred or forecast costs, while Price List APIs provide AWS service price information.

Tool / Feature Decision Guide

Choose Cost Explorer when the requirement emphasizes:

Charts or interactive exploration.
Understanding spending trends.
Finding which services, Availability Zones, or linked accounts contribute most to usage.
Forecasting spending for the next several months.

Choose CUR when the requirement emphasizes:

Detailed billing records.
Hourly, daily, or monthly granularity.
Product-resource or tag-level cost breakdowns.
Delivery to Amazon S3.
Building custom reporting or analysis from exported billing data.

Choose a Price List API when the requirement emphasizes:

Retrieving AWS service prices programmatically.
Querying prices in JSON through the Query API.
Using the bulk pricing interface.
Building a custom process that detects price changes and sends notifications.

Common Traps / Misconceptions

Confusing Cost Explorer with CUR: Cost Explorer is an interactive analysis and forecasting tool; CUR is a detailed report delivered to S3.
Assuming Cost Explorer is unlimited historical storage: The lecture specifies 13 months of cost data.
Overstating the forecast period: Cost Explorer forecasts up to 3 months into the future, not an unlimited period.
Forgetting linked accounts: When AWS Organizations is used, Cost Explorer can show cost and usage information across multiple linked accounts.
Mixing CUR and Price List APIs: The AWS CUR API manages reports, while Price List APIs query service prices.
Reversing the API formats: The Query API uses JSON, while the Bulk API is identified in the lesson as using HTML.
Treating CUR as real-time data: Reports can be updated up to three times per day, so the stated capability is periodic reporting rather than a continuous real-time stream.

Real-World Engineer / Analyst Notes

Start with Cost Explorer when investigating an unexpected increase in spending because its charts and filters help identify trends, services, Availability Zones, and linked accounts.
Use CUR when the investigation requires detailed records by product resource, tags, or specific time intervals.
Store CUR output in Amazon S3 when the organization needs a durable source for custom reporting or additional analysis.
Use the Price List APIs when the concern is the published price of an AWS service rather than analyzing historical account charges.
A practical cost-management workflow may use multiple tools: Cost Explorer for discovery, CUR for detailed analysis, and Price List APIs for programmatic price monitoring.

Quick Reference Summary

Tool or API	Primary purpose	Important details
Cost Explorer	Explore and forecast AWS spending	Free; 13 months of history; up to 3 months of forecasting
Cost and Usage Report (CUR)	Deliver detailed billing reports	Publishes to Amazon S3; supports time, product, resource, and tag breakdowns
AWS CUR API	Manage CUR reports	Create, retrieve, and delete reports
Price List Service API / Query API	Query AWS prices	JSON queries
AWS Price List API / Bulk API	Access bulk pricing information	HTML interface as described in the lesson

Flashcards

Q: A team wants interactive charts showing spending trends and a forecast for the next two months. Which AWS tool should it use?

A: Use Cost Explorer. It supports cost visualization, pattern discovery, and forecasts for up to three months into the future.

Q: What historical and forecast periods does Cost Explorer provide according to this lesson?

A: It provides cost data for the past 13 months and forecasts spending up to three months ahead.

Q: Which tool should you choose when costs must be broken down by product resource and tags and delivered to Amazon S3?

A: Choose the Cost and Usage Report (CUR), which publishes detailed billing reports to an S3 bucket and supports those breakdowns.

Q: An organization wants to compare usage across several AWS accounts. Which Cost Explorer context makes this possible?

A: With AWS Organizations, Cost Explorer can display information for multiple linked accounts, allowing account-level usage comparisons.

Q: What is the decisive difference between Cost Explorer and CUR?

A: Cost Explorer is primarily for interactive exploration and forecasting, whereas CUR provides detailed billing data for export and custom analysis through Amazon S3.

Q: How frequently can a Cost and Usage Report be updated according to the lecture?

A: It can be updated up to three times per day.

Q: Which API manages the lifecycle of Cost and Usage Reports?

A: The AWS CUR API can create, retrieve, and delete CUR reports.

Q: A custom application needs to query AWS prices using JSON. Which pricing interface should it use?

A: Use the Price List Service API, also called the Query API, because the lesson identifies it as the JSON-query interface.

Q: What is the role of the AWS Price List API, also called the Bulk API?

A: It provides the bulk pricing interface for querying AWS service prices, identified in the lesson as using HTML.

Q: A company wants to detect AWS price changes and send SMS notifications. Which category of tool supports this design?

A: The Price List APIs support retrieving pricing data that a custom monitoring system can check and use to trigger notifications.

Q: Which tool is best for discovering which Availability Zone has the most traffic or usage from a cost perspective?

A: Cost Explorer, because it can help examine service usage statistics by Availability Zone.

Q: Why might CUR be selected instead of Cost Explorer for a custom financial reporting system?

A: CUR provides detailed reports in Amazon S3 with hourly, daily, or monthly data and product, resource, and tag dimensions suitable for downstream analysis.

Practice Questions

Question 1

A cloud operations team needs to investigate a sudden increase in spending. It wants to interactively compare services, linked accounts, and Availability Zones before deciding whether detailed exports are necessary. Which tool is the best first choice?

A. AWS CUR API
B. Cost Explorer
C. Price List Service API
D. AWS Price List Bulk API

Correct answer: B. Cost Explorer

Cost Explorer is designed for interactive charts, cost-pattern discovery, and usage analysis across services, Availability Zones, and linked accounts.

Question 2

A finance team requires hourly billing data grouped by product resource and tags, with the report delivered to Amazon S3 for custom processing. Which solution fits the requirement?

A. Cost Explorer forecast
B. Cost and Usage Report
C. Price List Service API
D. AWS Organizations alone

Correct answer: B. Cost and Usage Report

CUR publishes detailed billing reports to S3 and supports hourly data plus product-resource and tag breakdowns.

Question 3

An internal application must retrieve AWS service prices through JSON queries. Which interface should the developers select?

A. AWS CUR API
B. Cost Explorer
C. Price List Service API / Query API
D. AWS Price List API / Bulk API

Correct answer: C. Price List Service API / Query API

The Query API is the Price List Service API component identified in the lesson as supporting JSON queries.

Question 4

An organization wants a custom process that checks AWS prices and sends an SMS alert when a price changes. Which tool category is most appropriate?

A. Cost Explorer only
B. AWS CUR API only
C. Price List APIs
D. Linked accounts in AWS Organizations

Correct answer: C. Price List APIs

Price List APIs provide pricing data that can be used by a custom monitoring system to detect changes and send notifications.

WordPress Metadata

Suggested Slug:
aws-cost-management-tools-cost-explorer-cur-price-list-apis

Meta Description:
Study Cost Explorer, the AWS Cost and Usage Report, and Price List APIs for analyzing spending, exporting detailed billing data, and querying AWS service prices.

Tags:
AWS, AWS Certified CloudOps Engineer, Cost Explorer, Cost and Usage Report, AWS billing, AWS Organizations, Price List API, cost optimization, Amazon S3, cloud operations