AWS Cloud Practitioner Study Notes · Part 9

AWS Cost and Billing: Pricing, Budgets, and Cost Management

AWS Cloud Practitioner study notes on AWS pricing principles, Free Tier, billing tools, budgets, cost reports, tags, and consolidated billing.

AWS cost questions often become easier when you identify the required action first: view the bill, analyse a trend, receive an alert, inspect detailed usage, right-size a resource, or combine multiple accounts. Each action maps to a different billing or cost-management feature.

This is Part 9 of the AWS Cloud Practitioner Study Notes series. Part 1 introduced the main EC2 purchasing models; this note connects pricing choices with billing visibility, cost controls, and account organisation.

The cost-management map

RequirementAWS featureExam clue
View the current billBilling and Cost Management dashboard and Bills pageCurrent charges, taxes, payments, or credits
Analyse spending over timeCost ExplorerHistorical costs, filters, trends, and forecasts
Receive a threshold notificationAWS BudgetsAlert when cost or usage approaches a limit
Export detailed usage recordsAWS Cost and Usage Report (CUR) or Data ExportsDetailed line-item billing analysis
Find right-sizing opportunitiesAWS Compute OptimizerResource recommendation based on utilisation
Find broad optimisation recommendationsAWS Trusted AdvisorIdle resources, limits, security, performance, and cost
Track spending by project or teamCost allocation tagsCategorise costs by tag
Combine multiple AWS accountsAWS Organizations consolidated billingOne bill and shared usage benefits

The tools complement one another. A dashboard shows what is happening now, Cost Explorer helps explain trends, Budgets warns about thresholds, and CUR supports detailed analysis.

1. AWS pricing principles

AWS commonly explains its pricing approach through three ideas:

Pay only for what you use

AWS uses a pay-as-you-go model for eligible usage. If an EC2 instance runs for two hours, you are charged for the applicable usage rather than purchasing a physical server for the whole year. Billing granularity and minimum charges vary by service and configuration, so check the service pricing page.

Stopping or deleting a resource does not automatically remove every related charge. Storage, public IPv4 addresses, snapshots, data transfer, load balancers, and other attached resources may have separate pricing.

Save when you commit or reserve

Predictable usage may qualify for lower rates through options such as Savings Plans or Reserved Instances. The discount comes with a commitment and service-specific rules. Part 1 compares the main purchasing models and their trade-offs.

Volume pricing may reduce average cost

Some services use tiered or volume pricing, where higher eligible usage can receive lower rates. This is not a universal promise that every AWS service becomes cheaper at any volume; always check the pricing page for the service, Region, and usage dimension.

2. AWS Free Tier

The AWS Free Tier provides limited offers for trying AWS services, but “free” always means free within the stated conditions. Offers can have limits on time, usage, account eligibility, Regions, or service features.

Study material commonly groups Free Tier offers into:

  • Always Free: available indefinitely within specified monthly limits.
  • 12 Months Free: available for an eligible period after account creation.
  • Short-term trials: available for a limited period or introductory usage window.

AWS account plans and Free Tier terms can change. Newer accounts may have different plan and credit options from legacy accounts, so use the current AWS Free Tier terms rather than memorising a quota from an old course.

Before creating resources, check:

  • Whether the service and feature are included
  • The monthly usage limit
  • The offer’s expiration date
  • Whether usage is aggregated across Regions or accounts
  • Related services that are not covered, such as data transfer or storage beyond the allowance

AWS Budgets and Free Tier usage alerts can help warn you about projected or actual usage, but they are not a substitute for deleting resources you no longer need.

3. Billing dashboard and Bills page

The Billing and Cost Management console gives you visibility into charges and account billing activity. Depending on permissions and the account structure, you can review:

  • Month-to-date estimated charges
  • Previous bills and invoices
  • Charges by service, account, or other dimensions
  • Payments, credits, and taxes
  • Free Tier usage and budget status
  • Cost recommendations and anomalies shown by the billing home page

If the exam asks, “Where can you view your AWS bill?”, the Billing dashboard or Bills page is the intended direction. It is different from Cost Explorer, which is designed for analysing cost and usage patterns.

4. AWS Cost Explorer

Cost Explorer helps you visualise and analyse AWS costs and usage. You can filter and group data by dimensions such as service, Region, linked account, usage type, or cost allocation tag.

Typical questions Cost Explorer can help answer include:

  • Why did this month cost more than the previous month?
  • Which service caused the increase?
  • Which account or project is spending the most?
  • What might the current month’s spending become?
  • How has usage changed over several months?

AWS documentation states that Cost Explorer can display up to 13 months of historical data and forecast up to 18 months, subject to the available data and current service behaviour. Cost data is refreshed regularly rather than appearing as a final invoice immediately.

Exam clues: historical spending, trends, filters, graphs, comparisons, and forecasts.

5. AWS Budgets

AWS Budgets is for planning and alerts. You define a budget amount or usage threshold, then configure notifications when actual or forecasted values approach or exceed it.

Budgets can cover use cases such as:

  • Monthly cost for an account or service
  • Usage for a selected AWS service
  • Reservation utilisation
  • Reservation coverage
  • Savings Plans utilisation or coverage
  • Free Tier usage monitoring

For example, a development account may have a monthly cost budget with email notifications at 50%, 80%, and 100% of the planned amount. The notification is an alert; it does not automatically stop every resource unless you deliberately configure an appropriate budget action and understand its effects.

Exam clues: alert, notification, threshold, forecasted spend, and spending limit.

6. AWS Cost and Usage Report

The AWS Cost and Usage Report (CUR) provides detailed billing and usage line items for an account or organisation. A report can be delivered to Amazon S3 for storage and further analysis.

Finance or platform teams can query the exported data with services such as Amazon Athena or visualise query results with Amazon QuickSight. This creates a flexible analysis path when the console’s summary views are not detailed enough.

Choose CUR when the question emphasises:

  • Detailed usage records
  • Resource-level or line-item analysis
  • Exporting billing data for a finance data pipeline
  • Analysing usage outside the Billing console

AWS also provides newer Data Exports capabilities, so the exact export feature should be selected based on the current billing documentation and reporting requirement.

7. AWS Compute Optimizer

AWS Compute Optimizer provides recommendations for supported resources by analysing configuration and utilisation data. It can help identify over-provisioned or under-provisioned resources and suggest more suitable options.

The important exam phrase is right-sizing recommendation. A resource using very little CPU or memory may not need its current size, but a recommendation still needs engineering review. CPU alone may not represent the workload’s bottleneck; memory, network, storage, latency, burst behaviour, and business-critical traffic also matter.

Compute Optimizer can provide recommendations for supported resources such as EC2 instances, Auto Scaling groups, EBS volumes, and Lambda functions. Supported resource types and recommendation details can change, so check the current service documentation.

8. AWS Trusted Advisor

Trusted Advisor provides checks and recommendations across areas such as:

  • Cost optimisation
  • Performance
  • Security
  • Fault tolerance
  • Service quotas

Cost-related examples may include idle resources, underutilised resources, or opportunities to remove waste. Trusted Advisor is broader than Compute Optimizer: it provides best-practice checks across several categories, while Compute Optimizer focuses on utilisation-based resource recommendations.

Neither service automatically fixes every issue. The team must validate the recommendation, understand the impact, and implement the change safely.

9. Cost allocation tags

Cost allocation tags help categorise spending by business dimensions such as project, environment, team, or application.

For example, resources may use tags such as:

Project     = Website
Environment = Production
Team        = Platform

After the relevant tags are activated for cost allocation, teams can use them in cost analysis and exports. This makes it easier to answer questions such as “How much did the Website project cost?” rather than seeing only one undifferentiated account total.

Tags for billing classification are not the same as IAM security controls. A tag does not grant or deny access by itself; access policies and resource policies determine permissions.

10. AWS Organizations and consolidated billing

AWS Organizations can combine billing and payment for multiple AWS accounts. A management account pays the consolidated bill for member accounts and can view aggregated organisation costs, subject to permissions and the organisation’s billing configuration.

Consolidated billing can provide:

  • One bill for multiple accounts in the same organisation billing boundary
  • Centralised payment and accounting
  • Combined usage for eligible volume pricing
  • Sharing of eligible Reserved Instance and Savings Plans benefits
  • Cost visibility by member account

A common structure is:

AWS Organizations
├── Development account
├── Test account
└── Production account

Separate accounts can improve isolation and governance, while consolidated billing simplifies payment. Consolidated billing does not make the accounts identical or remove the need for account-level security and cost ownership.

11. Billing support

All AWS customers can access account and billing help through AWS Support. Basic Support includes assistance for account and billing questions, but technical support features depend on the selected support plan.

This is a common exam distinction:

  • Billing or account issue: contact AWS Support.
  • General cost analysis: use Cost Explorer.
  • Spending threshold alert: use AWS Budgets.
  • Detailed billing export: use CUR or Data Exports.

Support-plan features and pricing can change, so verify current plan details before making a purchasing decision.

A practical cost-control workflow

For a small multi-account environment, a useful sequence is:

  1. Use AWS Organizations to separate development, test, and production accounts.
  2. Apply consistent cost allocation tags for project, environment, and owner.
  3. Configure AWS Budgets and Free Tier alerts.
  4. Use Cost Explorer to review trends and identify the main cost drivers.
  5. Export CUR or Data Exports to S3 when detailed finance analysis is required.
  6. Review Compute Optimizer and Trusted Advisor recommendations.
  7. Revisit pricing commitments only after usage becomes predictable.

This combines visibility, alerting, classification, analysis, and optimisation. No single tool answers every cost question.

Exam-ready memory aid

  • Billing dashboard: view current bills, payments, credits, and taxes.
  • Cost Explorer: analyse historical costs and forecast trends.
  • AWS Budgets: receive cost or usage alerts.
  • CUR: access detailed billing and usage data.
  • Compute Optimizer: receive right-sizing recommendations.
  • Trusted Advisor: receive broad best-practice recommendations.
  • Cost allocation tags: track spending by project or team.
  • Organizations: consolidate billing across multiple accounts.
  • Support: ask account and billing questions.

Conclusion

AWS cost management starts with understanding how usage becomes a bill, then choosing the right visibility and control for the question being asked. Pricing models influence the rate, the Billing dashboard shows charges, Cost Explorer explains trends, Budgets sends alerts, CUR supports detailed analysis, and Organizations combines account billing.

For the Cloud Practitioner exam, focus on the action words. View the bill in Billing, analyse trends with Cost Explorer, alert with Budgets, export details with CUR, right-size with Compute Optimizer, find broad recommendations with Trusted Advisor, and consolidate accounts with AWS Organizations.

Sources

Back to the journal