Step 4 — Billing & Pricing

Here’s a question worth sitting with for a second: if AWS bills you for exactly what you use, why does an entire exam domain exist around billing and pricing? Because “pay for what you use” still leaves a dozen decisions on the table — which pricing model, which support tier, which tool watches your spend before it spirals. This step is about those decisions.

Compute Pricing Models, Compared

AWS gives you several ways to pay for compute capacity, and the discount you get is directly tied to how much flexibility you give up.

FLEXIBILITY  ◄─────────────────────────────────────────►  DISCOUNT
(pay full price,        (commit ahead of time,           (deepest discount,
 no commitment,          predictable workload)            but AWS can reclaim
 change anytime)                                          capacity anytime)

   On-Demand      Savings Plans      Reserved Instances        Spot Instances

Compute Savings Plans are the pricing model AWS steers most customers toward today — rather than locking into one instance family the way older-style Reserved Instances did, a Savings Plan commits you to a consistent amount of hourly spend and automatically applies the discount across EC2, Fargate, and Lambda usage, whatever combination you end up using. It’s the flexible version of the same basic idea: commit ahead, pay less.

Spot Instances sit at the opposite end of the spectrum — the steepest possible discount, in exchange for accepting that AWS might reclaim that capacity on short notice when it’s needed elsewhere. That’s a perfectly reasonable trade for a machine learning training job or a batch render, and a terrible trade for a production database.

AWS Free Tier

New and existing customers get access to a set of offers designed to let you try services without committing real spend upfront. These generally fall into three buckets:

• Always free — available indefinitely, regardless of account age, up to a usage limit (for example, a monthly allotment of Lambda requests or a set amount of DynamoDB storage).
• 12 months free — available for the first year after account creation, covering commonly used services at introductory usage levels (for example, a certain amount of EC2 or S3 usage per month).
• Short-term trials — time-boxed trials on specific services that start counting down the moment you activate them, regardless of how much you actually use.

The trap the exam sets: Free Tier limits are usage caps, not a guarantee of zero charges. Exceed the included amount, and you’re billed at standard rates for the overage. Always-free offers don’t expire with account age; the 12-month category does.

Watching and Controlling Your Spend

AWS gives you several tools to understand, forecast, and react to your bill, and each one has a distinct job.

Cost Explorer          → Look backward and forward: visualize spend, spot trends, forecast future cost
AWS Budgets            → Set a threshold, get alerted when you approach or exceed it
Trusted Advisor        → Get recommendations across cost, performance, security, fault tolerance
Billing alarms          → CloudWatch-based alarm triggered by estimated charges crossing a limit

Cost Explorer is your analysis tool — a visual interface for breaking down historical spend by service, by linked account, or by tag, plus basic forecasting of where your bill is headed if current trends continue.

AWS Budgets is your alerting tool — you define a threshold (a dollar amount, a percentage of Free Tier usage, or a specific usage metric) and get notified as you approach or cross it. Cost Explorer tells you what happened; Budgets tells you when something’s about to happen that you asked to be warned about.

Trusted Advisor goes beyond just cost — it scans your account and flags opportunities across five categories: cost optimization, performance, security, fault tolerance, and service limits. The depth of Trusted Advisor’s checks depends on your support plan, which is where the next section comes in.

AWS Organizations and Consolidated Billing

Companies running multiple AWS accounts — one per team, one per environment, one per project — don’t want to reconcile a dozen separate invoices every month. AWS Organizations lets you group multiple accounts under a single management structure, and consolidated billing rolls all of those accounts into one bill.

The advantage isn’t just convenience. Combined usage across accounts can cross volume-pricing thresholds faster than any single account would alone, and it can share the benefit of Reserved Instance or Savings Plan discounts purchased in one account with others in the same organization. A ten-person startup with three accounts and a thousand-person enterprise with sixty accounts both benefit from the same basic mechanism: one bill, shared discounts, centralized visibility.

AWS Support Plans

AWS offers four support tiers, and CLF-C02 expects you to know roughly what separates them — not the exact pricing formula, but who each tier is built for.

The pattern to remember: every plan includes Basic-level access by default, and each tier up adds faster response times, broader support channels, and a more dedicated relationship with AWS. Enterprise is the only tier that includes a named Technical Account Manager — a recurring point in “which support plan includes a TAM” style questions.

Exam Focus: What Questions Test From This Step

• Matching a workload description to On-Demand, Reserved Instances, Savings Plans, or Spot Instances
• Knowing Compute Savings Plans apply flexibly across EC2, Fargate, and Lambda, unlike instance-locked Reserved Instances
• Free Tier categories: always free, 12 months free, and short trials — and that limits don’t guarantee zero cost
• Cost Explorer (analysis/forecasting) versus AWS Budgets (threshold alerting) versus Trusted Advisor (recommendations)
• Consolidated billing under AWS Organizations and why grouped accounts can unlock better pricing
• Which support plan tier includes 24/7 support, and which one adds a Technical Account Manager