Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/roxsross/aws-cloud-practitioner-complete-guide/llms.txt

Use this file to discover all available pages before exploring further.

One of the most common surprises for teams new to the cloud is an unexpectedly large AWS bill. AWS provides a purpose-built suite of tools to monitor, analyze, alert on, and optimize cloud spending before costs spiral out of control. Understanding these tools — and knowing which one to reach for in a given scenario — is a key component of Domain 4 on the CLF-C02 exam.
Cost management is a continuous cycle: Monitor what you spend → Analyze where it goes → Optimize to reduce waste → Govern with policies and alerts → and repeat. Each tool in this section maps to one or more phases of that cycle.

​
AWS Cost Explorer

AWS Cost Explorer is an interactive visualization and analysis tool that lets you understand your AWS spending over time.

Visualize Costs and Usage

Explore spending as line charts, bar charts, and stacked area graphs. Switch between daily or monthly granularity, and look back up to 12 months of historical data.

Filter and Group

Slice your data by service (EC2, S3, RDS), account (for Organizations), region, instance type, purchase option, or resource tag to isolate cost drivers.

Forecast Future Costs

Cost Explorer uses machine learning to project spending up to 12 months into the future based on your historical usage patterns, including seasonality and growth trends.

Savings Plan & RI Recommendations

Based on your On-Demand usage history, Cost Explorer generates specific Savings Plan or Reserved Instance purchase recommendations with projected savings amounts.
Cost Explorer must be enabled before it can display data — historical data is not retroactively backfilled before activation. Enable it early in an account’s lifecycle so you always have context for analysis.

​
AWS Budgets

AWS Budgets allows you to set custom cost and usage thresholds, then receive alerts via email or Amazon SNS when actual or forecasted spending is on track to exceed them.
Monitor total spending against a dollar amount. Example: alert the engineering manager when the production account is forecast to exceed $8,000 in the current month.
  • Set a monthly, quarterly, or annual budget
  • Alert on actual costs (already incurred) or forecasted costs (projected to be incurred by month-end)
  • Multiple alert thresholds per budget (e.g., 50%, 80%, 100%, 120%)
AWS Budgets is free for your first two budgets per month. Each additional budget costs 0.02perday(approximately0.02 per day (approximately 0.60/month). Budget Actions — automated responses that can stop EC2/RDS instances or apply IAM policies when a threshold is breached — are available with Business and Enterprise Support.

​
AWS Cost and Usage Report (CUR)

The Cost and Usage Report (CUR) is the most granular billing dataset AWS provides — a line-item breakdown of every charge for every AWS service.
The CUR contains hundreds of columns including:
  • Cost dimensions: unblended cost, blended cost (for Organizations), amortized cost (RIs and Savings Plans spread over the term), and net cost after credits
  • Usage dimensions: instance-hours, GB-hours, API request counts, data transfer volumes
  • Resource-level detail: ARN-level granularity so you can trace cost to a specific EC2 instance or S3 bucket
  • Tag values: all user-defined and AWS-generated tags you have activated for cost allocation
AWS delivers the CUR as compressed CSV files to an Amazon S3 bucket you specify — daily or hourly. From there you can:
  • Amazon Athena: Query the CUR with SQL directly from S3 for ad-hoc analysis
  • Amazon QuickSight: Build interactive dashboards and share them across your organization
  • AWS Glue + Redshift: Load CUR data into a data warehouse for custom BI tooling
The CUR is the go-to data source for detailed chargebacks, custom billing dashboards, and reconciling billing anomalies.

​
AWS Organizations and Consolidated Billing

AWS Organizations lets you manage multiple AWS accounts under a single umbrella, with centralized governance and billing.
1

Create an Organization

Designate one AWS account as the management (payer) account. All other accounts become member accounts that report their usage and receive a single consolidated bill.
2

Enable Consolidated Billing

All member account charges roll up into the management account’s monthly bill. This unlocks volume discount sharing — aggregate usage across all accounts qualifies for tiered pricing (e.g., S3 storage tiers, data transfer tiers) faster than any single account would on its own.
3

Organize Accounts with OUs

Group accounts into Organizational Units (OUs) that mirror your business structure — for example, separate OUs for Production, Development, and Sandbox environments, or by business unit (Finance, Engineering, Marketing).
4

Apply Service Control Policies (SCPs)

Attach Service Control Policies to the root, an OU, or an individual account to define maximum permissions. SCPs act as guardrails — they cannot grant permissions, only restrict them. Use SCPs to prevent member accounts from launching resources in unapproved regions or disabling CloudTrail.
SCPs in AWS Organizations operate as a deny-override mechanism: even if an IAM policy in a member account grants a permission, an SCP that denies it will always win. Carefully test SCPs before applying them broadly to avoid locking out accounts.

​
AWS Compute Optimizer

AWS Compute Optimizer uses machine learning to analyze your historical resource utilization and generate right-sizing recommendations.

EC2 Instances

Identifies over-provisioned or under-provisioned instances based on CPU, memory, network, and disk I/O utilization. Recommends a specific instance type change with projected cost impact.

Auto Scaling Groups

Recommends optimal instance types and sizes for EC2 Auto Scaling Groups, helping you balance performance headroom against unnecessary compute spend.

AWS Lambda

Analyzes memory size versus actual memory used during function invocations and recommends memory configuration changes that reduce cost without degrading performance.

Amazon EBS Volumes

Identifies EBS volumes where provisioned IOPS or throughput significantly exceeds actual utilization, recommending a cheaper volume type or smaller provisioned capacity.

​
AWS Trusted Advisor — Cost Pillar

AWS Trusted Advisor provides real-time guidance across five pillars. The Cost Optimization checks are especially relevant for the CLF-C02 exam.
  • Idle EC2 instances: Flags instances with low CPU utilization (≤ 10%) over the past 14 days
  • Underutilized EBS volumes: Identifies volumes with very low IOPS activity
  • Unassociated Elastic IP addresses: Elastic IPs not attached to a running instance incur a small hourly charge — Trusted Advisor surfaces these so they can be released
  • Reserved Instance purchase recommendations: Highlights On-Demand usage patterns that suggest RI purchases would reduce costs
  • Low-utilization RDS instances: RDS instances with minimal database connections or CPU usage
The 7 core Trusted Advisor checks (available on Basic and Developer support) are security-focused. The full cost optimization checks require Business or Enterprise support. See the Support Plans page for details.

​
Tagging for Cost Allocation

Resource tags are key-value pairs you attach to AWS resources. When activated as Cost Allocation Tags in the Billing Console, they become filterable dimensions in Cost Explorer, AWS Budgets, and the CUR.

​
Setting Up Cost Monitoring: A Step-by-Step Workflow

1

Enable Cost Explorer

In the AWS Billing Console, enable Cost Explorer. It typically takes 24 hours to display initial data, so activate it on day one of any new account.
2

Set Budget Alerts in AWS Budgets

Create at minimum a monthly Cost Budget for each significant environment or project. Set alerts at 50%, 80%, and 100% of your expected spend — and add a forecasted cost alert so you are warned before the budget is breached, not after.
3

Tag All Resources

Establish a mandatory tagging convention and apply it to every resource. Use Environment, Project, Team, and Owner as a starting baseline, then activate those tags for cost allocation in the Billing Console.
4

Review Trusted Advisor Recommendations Monthly

Schedule a monthly review of Trusted Advisor’s Cost Optimization checks. Idle resources and unassociated Elastic IPs accumulate quietly — a monthly sweep prevents unnecessary charges.
5

Enable Consolidated Billing via AWS Organizations

If you operate multiple accounts, establish an AWS Organization to consolidate billing. This enables volume discounts across accounts and gives you a single pane of glass for organization-wide cost analysis in Cost Explorer.
Use AWS Budgets to get email alerts before you exceed your budget — not after. A forecasted budget alert at 80% gives you days to take corrective action; discovering the overage on your month-end bill gives you nothing but regret.

Build docs developers (and LLMs) love

Get started for freeTalk to us