Skip to content

CLF-C02 Study Notes: Task Statement 4.2 - Understand resources for billing, budget, and cost management

This task focuses on the AWS tools and practices used to monitor usage, allocate costs, set budgets, optimize resources, and manage billing across accounts.

1. Cost management fundamentals

A good cost-management strategy should include:

  • Defining cost and usage metrics
  • Setting target goals and budgets
  • Establishing and enforcing a tagging strategy
  • Using cost allocation tags
  • Monitoring resource utilization
  • Reviewing the architecture regularly
  • Rightsizing or removing underutilized resources
  • Selecting appropriate storage and data-transfer options

AWS costs can change as workloads, traffic, and architecture change. Cost monitoring should therefore be continuous rather than a one-time activity.

Common metrics to monitor

Depending on the service, monitor metrics such as:

  • CPU utilization
  • Memory utilization
  • Storage capacity
  • EBS IOPS
  • Network traffic
  • Number of running instances
  • Data transfer volume
  • S3 object access patterns

Monitoring these metrics helps identify resources that should be:

  • Downsized
  • Increased
  • Replaced with a different resource type
  • Automatically scaled
  • Deleted

2. Cost allocation tags

Cost allocation tags are tags used to organize and analyze AWS costs.

Example tags:

Environment = Production
Department = Finance
Application = WebApp
Project = Migration
CostCenter = 12345

Cost allocation tags can be used to:

  • Filter cost views in AWS Cost Explorer
  • Allocate costs to departments or projects
  • Track production versus development spending
  • Support internal chargeback or showback processes

Important considerations

  • Tags must be applied consistently to resources.
  • A tagging strategy should be defined and enforced.
  • Not every AWS resource supports the same tagging capabilities.
  • Tags may need to be activated as cost allocation tags before they appear in billing reports.

Exam tip

If a question asks how to determine which department or project incurred AWS costs, the likely answer involves:

  • Cost allocation tags
  • AWS Cost Explorer
  • AWS Cost and Usage Reports

3. AWS Cost Explorer

AWS Cost Explorer provides an interactive, high-level view of AWS costs and usage.

It can be used to:

  • View historical and current costs
  • Filter by service, Region, account, or tag
  • Group costs by dimensions
  • Identify spending trends
  • Drill down into cost details
  • Forecast future costs

Best use case

Use Cost Explorer when you need:

An interactive, visual, and relatively high-level analysis of AWS costs.

Cost Explorer versus AWS Cost and Usage Reports

Feature AWS Cost Explorer AWS Cost and Usage Reports
Main purpose Interactive cost analysis Detailed billing and usage data
Level of detail High-level with drill-down Most granular
Typical use View trends and filter costs Detailed analysis and custom reporting
Output Console-based visual reports Data delivered to Amazon S3
Integration Built-in cost views Can be analyzed with Athena, Redshift, QuickSight, or other tools

Exam trap

  • Cost Explorer is generally the answer for interactive cost analysis.
  • Cost and Usage Reports are generally the answer for the most detailed or granular billing data.

4. AWS Cost and Usage Reports

The AWS Cost and Usage Report (CUR) provides detailed information about AWS usage and costs.

Reports can include breakdowns by:

  • Hour
  • Day
  • Month
  • Service or product
  • Linked account
  • Region
  • Usage type
  • Resource
  • Cost allocation tag

The report can be delivered to Amazon S3 and analyzed using services such as:

  • Amazon Athena
  • Amazon Redshift
  • Amazon QuickSight
  • Other analytics tools

Best use case

Use the Cost and Usage Report when you need:

The most granular cost and usage information for detailed analysis, reporting, or chargeback.

5. AWS Budgets and billing alerts

AWS Budgets

AWS Budgets allows you to set custom budgets for:

  • Cost
  • Usage
  • Reservation utilization
  • Reservation coverage
  • Savings Plans utilization
  • Savings Plans coverage

You can configure notifications when actual or forecasted usage exceeds a threshold.

Example thresholds:

  • Alert at 80% of monthly budget
  • Alert at 100% of monthly budget
  • Alert when forecasted costs are expected to exceed the budget

AWS Budgets can also trigger automated actions, depending on the budget configuration. For example, an action may restrict or modify certain resources to help control costs.

Billing alarms

Billing alarms can be used to alert you when estimated AWS charges exceed a specified amount.

These are commonly associated with:

  • Amazon CloudWatch billing metrics
  • Email or notification alerts
  • Free Tier usage monitoring

Free Tier alerts

AWS can notify you when your usage approaches or exceeds Free Tier limits.

Exam tip

When the question asks for:

  • Budget thresholds and cost notifications → AWS Budgets
  • Monitoring estimated billing charges with an alarm → CloudWatch billing alarms
  • Monitoring Free Tier usage → Free Tier alerts

6. Amazon CloudWatch for cost monitoring

Amazon CloudWatch primarily monitors operational metrics, logs, and alarms.

It can be used to monitor:

  • CPU utilization
  • Network traffic
  • Storage-related metrics
  • Application metrics
  • Billing metrics
  • Resource health

CloudWatch alarms can trigger notifications or automated actions when a metric crosses a threshold.

CloudWatch versus Cost Explorer

Service Primary purpose
CloudWatch Operational monitoring, metrics, logs, and alarms
Cost Explorer Interactive cost and usage analysis
AWS Budgets Budget thresholds and cost notifications
Cost and Usage Reports Detailed billing and usage data

Exam trap

CloudWatch is not primarily a billing-analysis tool. If the requirement is to analyze spending by service, account, or tag, Cost Explorer is usually more appropriate.

7. Amazon QuickSight

Amazon QuickSight is a business intelligence and data visualization service.

It can be used to:

  • Create dashboards
  • Build visual reports
  • Analyze AWS Cost and Usage Reports
  • Share financial and operational insights
  • Create custom visualizations

QuickSight is not itself the source of detailed billing data. It can visualize data obtained from sources such as the Cost and Usage Report.

8. AWS Organizations and consolidated billing

AWS Organizations allows an organization to centrally manage multiple AWS accounts.

Capabilities include:

  • Centralized account management
  • Consolidated billing
  • Service Control Policies (SCPs)
  • Organizational units
  • Centralized governance and access control
  • Sharing certain resources across accounts

Consolidated billing benefits

With consolidated billing:

  • One payer account receives the organization’s bill.
  • The organization receives a combined view of costs.
  • Costs can still be analyzed per linked account.
  • Usage from accounts may be combined for volume pricing.
  • Some volume discounts may be applied based on combined usage.
  • The organization can simplify payment and billing administration.

For billing purposes, AWS can treat usage across accounts in an organization as combined when determining applicable volume pricing tiers.

Important distinction

Consolidated billing does not mean that all accounts lose their individual cost visibility. Detailed costs can still be reported for each linked account.

Exam tip

If the question asks which feature can provide volume discounts across multiple AWS accounts, the answer is generally:

Consolidated billing through AWS Organizations.

9. AWS Control Tower

AWS Control Tower helps set up and govern a multi-account AWS environment.

It provides:

  • A controlled landing zone
  • Account provisioning
  • Governance guardrails
  • Centralized account management
  • Compliance and security controls

Comparison

Service Main focus
AWS Organizations Manage accounts, policies, and consolidated billing
AWS Control Tower Set up and govern a multi-account environment using managed guardrails

Control Tower uses AWS Organizations but provides additional governance and landing-zone capabilities.

10. AWS Billing Conductor

AWS Billing Conductor is a custom billing service intended to support:

  • Showback
  • Chargeback
  • Custom billing arrangements
  • Internal billing models for enterprise customers
  • AWS Solution Provider billing workflows

Definitions

  • Showback: Displaying costs to a department or customer for awareness.
  • Chargeback: Assigning or charging costs to a department or customer.

Exam focus

At the CLF-C02 level, remember the high-level purpose:

Billing Conductor supports customized billing views and chargeback or showback workflows.

11. Rightsizing and automatic scaling

Rightsizing

Rightsizing means selecting the appropriate resource size and type for the workload.

Examples:

  • Moving an underutilized EC2 instance to a smaller instance type
  • Changing an overprovisioned EBS volume type
  • Removing unused resources
  • Reducing allocated capacity when demand is low

Use monitoring data to establish a usage baseline before changing resources.

AWS Auto Scaling

AWS Auto Scaling helps maintain the appropriate amount of capacity as demand changes.

It can help reduce costs by:

  • Scaling out when demand increases
  • Scaling in when demand decreases
  • Avoiding excessive idle capacity

Amazon EC2 Auto Scaling

Amazon EC2 Auto Scaling adjusts the number of EC2 instances in an Auto Scaling group based on demand or policies.

Services that scale automatically

Some AWS services scale capacity automatically with usage, including:

  • AWS Lambda
  • Amazon API Gateway

Exam trap

  • Auto Scaling helps adjust capacity automatically.
  • Rightsizing is the process of selecting an appropriately sized resource based on actual usage.
  • Auto Scaling does not automatically mean that every workload will cost less; poorly designed scaling policies can still create unnecessary costs.

12. Trusted Advisor and cost optimization

AWS Trusted Advisor provides recommendations across areas such as:

  • Cost optimization
  • Performance
  • Security
  • Fault tolerance
  • Service limits

For cost optimization, Trusted Advisor can identify issues such as:

  • Underutilized Amazon EBS volumes
  • Idle or underutilized resources
  • Opportunities to reduce unnecessary spending

Exam tip

If a question asks which service provides recommendations about underutilized AWS resources, the likely answer is:

AWS Trusted Advisor.

13. EBS cost optimization

Amazon EBS costs can be optimized by reviewing:

  • Volume size
  • Volume type
  • Provisioned IOPS
  • Actual IOPS usage
  • Whether the volume is still needed
  • Snapshot retention

If you pay for a highly performant volume type but do not use its performance capacity, you may be able to switch to a lower-cost volume type.

Example

If an application uses only a small fraction of the IOPS provisioned for an EBS volume, consider whether a less expensive volume type can meet the workload’s requirements.

Exam trap

Do not optimize solely for the lowest storage price. The selected EBS volume must still satisfy:

  • Performance requirements
  • IOPS requirements
  • Throughput requirements
  • Availability and workload needs

14. Data lifecycle management

Automatically deleting data that is no longer required can reduce storage costs.

Relevant services include:

Amazon Data Lifecycle Manager

Amazon Data Lifecycle Manager can automate the management of:

  • EBS snapshots
  • EBS-backed AMI lifecycles

It can create and delete snapshots according to defined policies.

AWS Backup

AWS Backup centrally manages backups for supported AWS services.

It can help define:

  • Backup schedules
  • Retention periods
  • Lifecycle policies
  • Centralized backup management

Comparison

Service Main use
Amazon Data Lifecycle Manager Automate EBS snapshot and AMI lifecycle management
AWS Backup Centrally manage backups across supported AWS services

Exam tip

If the requirement is specifically to automatically delete old EBS snapshots, Amazon Data Lifecycle Manager is a strong candidate. If the requirement is centralized backup management across multiple AWS services, AWS Backup is more appropriate.

15. Amazon S3 storage cost optimization

Amazon S3 provides multiple storage classes. The correct choice depends on:

  • How frequently data is accessed
  • How quickly data must be retrieved
  • How long data is retained
  • Whether data needs to be available immediately
  • Whether access patterns are predictable or unpredictable

You do not generally need to memorize exact S3 prices for the CLF-C02. Understand the cost and retrieval trade-offs.

Common S3 storage classes

Storage class Typical use General cost and retrieval characteristics
S3 Standard Frequently accessed data Higher storage cost, fast and immediate access
S3 Intelligent-Tiering Data with changing or unknown access patterns Automatically moves objects between access tiers
S3 Standard-IA Infrequently accessed data that still requires rapid access Lower storage cost, retrieval charges apply
S3 One Zone-IA Infrequently accessed, re-creatable data Lower cost, stored in one Availability Zone
S3 Glacier Instant Retrieval Archive data requiring immediate access Lower storage cost than Standard, designed for instant retrieval
S3 Glacier Flexible Retrieval Archive data accessed infrequently Lower storage cost, retrieval can take minutes to hours
S3 Glacier Deep Archive Very rarely accessed long-term archives Lowest storage cost, longest retrieval time

Important trade-offs

Lower-cost storage classes may have:

  • Retrieval charges
  • Minimum storage-duration charges
  • Minimum object-size requirements
  • Longer retrieval times
  • Reduced resilience or availability characteristics, depending on the class

Exam tip

Choose the storage class based on the scenario:

  • Frequent access → S3 Standard
  • Unknown or changing access patterns → S3 Intelligent-Tiering
  • Infrequent but immediate access → Standard-IA or Glacier Instant Retrieval
  • Long-term archive with rare access → Glacier Flexible Retrieval or Glacier Deep Archive
  • Data that can be recreated and does not need multi-AZ storage → One Zone-IA

16. S3 Lifecycle Configuration

An S3 Lifecycle Configuration allows you to automate actions on objects.

Lifecycle rules can:

  • Transition objects to another storage class
  • Expire or delete objects
  • Delete incomplete multipart uploads
  • Transition current or previous object versions

Example

A lifecycle policy could:

  1. Store new objects in S3 Standard.
  2. Transition them to S3 Standard-IA after 30 days.
  3. Transition them to S3 Glacier after 90 days.
  4. Delete them after a specified retention period.

Lifecycle Configuration versus Intelligent-Tiering

Feature S3 Lifecycle Configuration S3 Intelligent-Tiering
Decision basis Rules based on age or object state Actual access patterns
Typical use Predictable data lifecycle Unknown or changing access patterns
Automatically changes storage class Yes Yes
Automatically responds to access changes Not generally Yes

Exam trap

  • “Automatically transition objects after a period of time” → S3 Lifecycle Configuration
  • “Automatically move each object to the most cost-effective access tier as access patterns change” → S3 Intelligent-Tiering

17. S3 Requester Pays

S3 Requester Pays allows the requester to pay for:

  • Data access requests
  • Data transfer charges associated with downloading the data

Normally, the bucket owner pays for requests and data transfer associated with access to the bucket.

Requester Pays is useful when:

  • A bucket contains publicly shared or research data
  • The bucket owner does not want to pay for all access
  • Consumers of the data should bear the request and download costs

Exam trap

Requester Pays does not mean that the requester pays every possible S3 cost. The feature primarily transfers responsibility for request and data-transfer charges associated with accessing the bucket.

18. Data migration and transfer services

AWS provides several options for moving data into and out of AWS.

AWS DataSync

AWS DataSync is used to transfer data between:

  • On-premises storage and AWS
  • AWS storage services
  • AWS Regions

It is appropriate for:

  • Online data transfers
  • File-system migrations
  • Scheduled or recurring transfers
  • Synchronizing large amounts of data

AWS Snow Family

The Snow Family provides physical devices for offline data transfer and edge computing.

Examples include:

  • AWS Snowcone: Small, portable data transfer and edge device
  • AWS Snowball Edge: Physical device for transferring large amounts of data
  • AWS Snowmobile: A shipping-container-sized data transfer solution for extremely large datasets

When to consider Snowball

Snowball is often a strong choice when:

  • The dataset is very large
  • Network transfer would take too long
  • The network connection has limited bandwidth
  • The transfer must be secure
  • Data must be transferred from on premises to AWS

AWS Transfer Family

AWS Transfer Family provides managed file transfer into and out of Amazon S3 or Amazon EFS using protocols such as:

  • SFTP
  • FTPS
  • FTP

It is useful when existing users or applications require traditional file-transfer protocols.

AWS Storage Gateway

AWS Storage Gateway connects on-premises environments with AWS storage services.

It supports hybrid storage use cases such as:

  • File-based access
  • Volume-based access
  • Virtual tape workflows

Comparison

Service Best suited for
AWS DataSync Online, automated, high-speed data transfer
Snowball Edge Offline transfer of large datasets
Snowmobile Extremely large-scale data migration
AWS Transfer Family Managed SFTP, FTPS, or FTP access
AWS Storage Gateway Hybrid on-premises and AWS storage integration

19. Data-transfer cost considerations

Data-transfer charges depend on:

  • Direction of transfer
  • AWS service
  • Region
  • Whether traffic crosses Availability Zones
  • Whether traffic crosses AWS Regions
  • Whether data is transferred to the public internet

Key exam concepts

  • Data transferred between different AWS Regions generally incurs charges.
  • Data transferred from AWS to the public internet generally incurs data-transfer-out charges.
  • Data transfer within AWS may be free or charged depending on the services, Regions, and network path.
  • Always evaluate architecture placement and data movement to reduce unnecessary transfer costs.

Example

If an application frequently moves large volumes of data between two AWS Regions, those inter-Region transfers can significantly increase costs.

Exam trap

Do not assume that all data transfer inside AWS is free. Charges may apply when data crosses:

  • Regions
  • Availability Zones
  • Certain service boundaries
  • The public internet

20. AWS Pricing Calculator

The AWS Pricing Calculator estimates the monthly cost of AWS services based on expected usage.

It can be used before deployment to:

  • Estimate the cost of a proposed architecture
  • Compare service options
  • Model different Regions
  • Estimate compute, storage, and data-transfer costs
  • Support migration planning and budgeting

Exam tip

If the question asks how to estimate the expected monthly cost of a planned AWS workload, choose:

AWS Pricing Calculator.

It provides an estimate, not a guaranteed final bill.

21. Cost optimization decision guide

Requirement Likely AWS resource or feature
Interactive view of AWS costs AWS Cost Explorer
Most detailed hourly or resource-level billing data AWS Cost and Usage Report
Create a spending limit and receive alerts AWS Budgets
Alarm when estimated billing charges exceed a threshold CloudWatch billing alarm
Visualize billing data in dashboards Amazon QuickSight
Attribute costs to teams or projects Cost allocation tags
Combine billing across accounts AWS Organizations consolidated billing
Find underutilized resources AWS Trusted Advisor
Adjust EC2 capacity to demand EC2 Auto Scaling
Automatically move S3 objects by age S3 Lifecycle Configuration
Automatically optimize S3 tier based on access patterns S3 Intelligent-Tiering
Automate EBS snapshot retention Amazon Data Lifecycle Manager
Centralize backups across AWS services AWS Backup
Estimate planned AWS costs AWS Pricing Calculator
Transfer large data sets offline Snowball Edge
Transfer extremely large data sets Snowmobile
Use SFTP, FTPS, or FTP with S3/EFS AWS Transfer Family

22. Common exam tips and traps

  1. Cost Explorer versus Cost and Usage Report
  2. Cost Explorer: interactive and high-level.

  3. CUR: detailed and granular.

  4. Budgets versus CloudWatch

  5. AWS Budgets: budget thresholds and notifications/actions.

  6. CloudWatch: metrics, logs, and alarms, including billing alarms.

  7. Lifecycle policies versus Intelligent-Tiering

  8. Lifecycle: transition based on rules such as object age.

  9. Intelligent-Tiering: transition based on changing access patterns.

  10. S3 Standard-IA is not always cheaper

  11. Retrieval charges and minimum storage-duration charges can make it more expensive for frequently accessed data.

  12. One Zone-IA has reduced resilience

  13. It stores data in one Availability Zone and is intended for data that can be recreated.

  14. Consolidated billing does not eliminate account-level reporting

  15. The organization receives a combined bill, while costs can still be analyzed by linked account.

  16. Trusted Advisor recommends; it does not automatically rightsize every resource

  17. Monitoring and architectural decisions are still required.

  18. Data transfer between Regions is generally chargeable

  19. Do not assume cross-Region transfer is free.

  20. Snowball versus Snowmobile

  21. Snowball Edge: large datasets.

  22. Snowmobile: extremely large, exabyte-scale migrations.

  23. Pricing Calculator provides estimates

    • It does not guarantee the exact final AWS bill.

23. Practice questions

Question 1

A company wants an interactive dashboard showing AWS costs by service, linked account, and cost allocation tag. Which AWS service should it use?

A. AWS Cost and Usage Report
B. AWS Cost Explorer
C. AWS Trusted Advisor
D. AWS Pricing Calculator

Answer: B. AWS Cost Explorer

Explanation: Cost Explorer provides interactive cost views and supports filtering and grouping by dimensions such as service, account, and tags.

Question 2

A finance team needs the most granular AWS billing data, including hourly usage and resource tags, for analysis using Amazon Athena. Which solution should the team use?

A. AWS Budgets
B. AWS Cost Explorer
C. AWS Cost and Usage Report
D. Amazon CloudWatch

Answer: C. AWS Cost and Usage Report

Explanation: The Cost and Usage Report provides detailed billing data and can deliver it to Amazon S3 for analysis with Athena.

Question 3

A company wants to receive an alert when its forecasted monthly AWS costs are expected to exceed a defined budget. Which service should it use?

A. AWS Budgets
B. Amazon Inspector
C. AWS Pricing Calculator
D. AWS Organizations

Answer: A. AWS Budgets

Explanation: AWS Budgets supports cost thresholds and notifications based on actual or forecasted spending.

Question 4

A company stores objects in Amazon S3. The objects should automatically move to a lower-cost storage class after 90 days and be deleted after one year. Which feature should be used?

A. S3 Intelligent-Tiering
B. S3 Lifecycle Configuration
C. S3 Requester Pays
D. S3 Versioning

Answer: B. S3 Lifecycle Configuration

Explanation: Lifecycle rules can transition and expire objects based on time or other object conditions.

Question 5

A company has unpredictable access patterns for objects in an S3 bucket. The company wants Amazon S3 to automatically move objects between access tiers as the access patterns change. Which storage class should it use?

A. S3 Standard-IA
B. S3 One Zone-IA
C. S3 Intelligent-Tiering
D. S3 Glacier Deep Archive

Answer: C. S3 Intelligent-Tiering

Explanation: Intelligent-Tiering automatically moves individual objects between access tiers based on changing access patterns.

Question 6

A company wants to transfer 250 TB of data from on-premises servers to Amazon S3. The available network connection is too slow to complete the transfer within the required timeframe. Which option is most appropriate?

A. AWS Snowball Edge
B. Amazon CloudWatch
C. AWS Budgets
D. Amazon QuickSight

Answer: A. AWS Snowball Edge

Explanation: Snowball Edge provides physical devices for secure offline transfer of large datasets to AWS.

Question 7

A company has multiple AWS accounts and wants to combine usage to potentially qualify for volume pricing discounts. Which feature should it use?

A. AWS Cost Explorer
B. AWS Organizations consolidated billing
C. AWS Pricing Calculator
D. AWS Billing Conductor only

Answer: B. AWS Organizations consolidated billing

Explanation: Consolidated billing combines billing and, where applicable, usage across accounts for volume pricing calculations.

Question 8

A company wants recommendations about unused or underutilized EBS volumes. Which AWS service can provide these recommendations?

A. AWS Trusted Advisor
B. Amazon S3
C. AWS DataSync
D. Amazon QuickSight

Answer: A. AWS Trusted Advisor

Explanation: Trusted Advisor provides cost optimization recommendations, including recommendations about underutilized resources.

Question 9

A company wants to charge data consumers for the S3 requests and data downloaded from a shared bucket instead of paying for those costs itself. Which feature should be enabled?

A. S3 Lifecycle Configuration
B. S3 Intelligent-Tiering
C. S3 Requester Pays
D. S3 Transfer Acceleration

Answer: C. S3 Requester Pays

Explanation: Requester Pays transfers responsibility for request and associated data-transfer charges to the requester.

Question 10

Which service estimates the monthly cost of a planned AWS architecture based on expected usage?

A. AWS Pricing Calculator
B. AWS Cost and Usage Report
C. AWS Budgets
D. AWS Trusted Advisor

Answer: A. AWS Pricing Calculator

Explanation: The Pricing Calculator estimates expected AWS service costs before deployment.