Module 10: Billing Tools, Cost Management, and AWS Support Plans

Step 1 – Where This Module Fits (Link to Modules 8 & 9)

In Modules 8 and 9 you learned:

• Module 8: How users and systems interact with AWS (console, CLI, SDKs) and basic operations.
• Module 9: How AWS pricing models work (On-Demand, Savings Plans, Reserved Instances, etc.) and basic cost optimization ideas.

This module focuses on "Now what?" after you start using AWS:

• How do you see what you’re spending?
• How do you analyze trends and find cost drivers?
• How do you set alerts so costs don’t surprise you?
• What tools help you estimate costs before you deploy?
• If something breaks or you’re stuck, which AWS Support plan gives you the help you need?

You’ll learn to:

1. Recognize when to use AWS Billing & Cost Management console, AWS Cost Explorer, and AWS Budgets.
2. Understand AWS Pricing Calculator and TCO (Total Cost of Ownership) tools at a conceptual level.
3. Distinguish among AWS Support plans and match them to exam-style scenarios.

Keep the CLF-C02 exam in mind: you don’t need to memorize every feature, but you must know which tool or plan is appropriate for a given situation.

Step 2 – AWS Billing & Cost Management Console: Your Cost Home Base

The AWS Billing & Cost Management console is where you go in the AWS Management Console to manage all things billing.

How to access it (step-by-step):

1. Sign in to the AWS Management Console.
2. In the search bar at the top, type “Billing”.
3. Click “Billing and Cost Management”.

Key sections you should recognize for the exam:

• Bills
• Shows your current and past invoices by month.
• Breaks down charges by service (e.g., Amazon EC2, S3) and region.
• Useful when you want a detailed statement of what you owe.

• Cost Explorer (link from Billing console)
• Opens the Cost Explorer service for deeper analysis (we’ll cover it next).

• Budgets (link from Billing console)
• Opens AWS Budgets to set cost/usage/coverage/RI/Savings Plans budgets.

• Payment methods & tax settings
• Add/modify credit cards, view tax invoices, manage tax settings.

• Preferences
• Turn on Billing alerts (so CloudWatch can send cost notifications).
• Control PDF invoice delivery and IAM access to billing.

When to use the Billing console (exam-style thinking):

• You need to download last month’s invoice for accounting.
• You want to see exactly how much S3 in us-east-1 cost last month.
• You want to update your credit card or billing contact.

Think of Billing as the “bank statement” and settings view, not the main analysis tool.

Step 3 – Quick Walkthrough: Reading Your AWS Bill

Imagine you’re running a student project on AWS and your professor asks: “Why did our AWS bill jump in January?”

Walkthrough using the Billing console:

1. Go to Billing & Cost Management.
2. In the left menu, click Bills.
3. At the top, choose January 2026 from the month selector.
4. Scroll down to see a list of services: e.g., Amazon EC2, Amazon S3, Amazon RDS.
5. You notice Amazon EC2 is much higher than in December.
6. Expand Amazon EC2:

• You see charges grouped by region (e.g., US East (N. Virginia)).
• Under that, you see On-Demand Linux t3.medium instance-hours.

1. You realize someone launched a bigger instance type for a data processing job and forgot to shut it down.

Key takeaway:

Use the Bills page when you need a clear, invoice-like breakdown of what you owe and which services/regions contributed to that bill.

Step 4 – AWS Cost Explorer: Analyzing Trends and Cost Drivers

AWS Cost Explorer is the main tool for visual cost analysis over time.

What Cost Explorer does well:

• Shows graphs of your cost and usage over days, months, or custom periods.
• Lets you filter and group by:
• Service (EC2, S3, RDS, etc.)
• Region
• Linked account (in AWS Organizations)
• Usage type (e.g., `BoxUsage:t3.micro`)
• Tags (e.g., `Environment=Prod`)
• Helps you see trends (cost going up/down) and cost drivers (which service or tag is responsible).
• Includes forecasting (e.g., predicted cost for the month based on current usage).

How to open Cost Explorer (step-by-step):

1. From the Billing & Cost Management console, click Cost Explorer in the left menu.
2. Click Launch Cost Explorer (first time you may need to enable it).
3. Use the prebuilt reports (e.g., Monthly costs by service) as a starting point.

When to use Cost Explorer (vs Billing console):

• Billing console (Bills page):
• You want a static invoice for a specific month.
• Cost Explorer:
• You want to see trends (e.g., “Is my EC2 cost increasing over the last 6 months?”).
• You want to analyze which tag or project is driving cost.

For CLF-C02, you should recognize Cost Explorer = visual analysis + trends + filters.

Step 5 – Thought Exercise: Cost Explorer vs Billing Console

Decide which tool you’d use for each situation. Think it through before checking the suggested answers below.

Scenario A

Your finance department needs a PDF-style invoice for December 2025 to attach to their records.

• Which tool? Billing console (Bills) or Cost Explorer?

Scenario B

Your team lead asks: “Our total cost doubled in the last 3 months. Is it S3, EC2, or something else?”

• Which tool? Billing console or Cost Explorer?

Scenario C

You want to see how much your development environment (tagged `Environment=Dev`) costs compared to `Environment=Prod`.

• Which tool? Billing console or Cost Explorer?

---

Suggested answers (don’t peek until you’ve thought about it):

• A → Billing console (Bills page): You need an invoice-like breakdown.
• B → Cost Explorer: You need trend analysis and to group by service.
• C → Cost Explorer: You need to filter/group by tags, which is a core Cost Explorer use case.

If you mixed any of these up, reread Steps 2–4 and focus on the phrase:

> Billing = invoice; Cost Explorer = analysis.

Step 6 – AWS Budgets: Setting Alerts and Guardrails

AWS Budgets lets you set custom budgets and receive alerts when you approach or exceed them.

You can create budgets for:

• Cost (e.g., total monthly cost, or cost for a specific service or tag)
• Usage (e.g., GB of data transfer, EC2 hours)
• RI/Savings Plans coverage & utilization (more advanced, not deeply tested at CLF-C02 level)

Basic workflow (step-by-step):

1. From Billing & Cost Management, click Budgets.
2. Choose Create budget.
3. Select Cost budget (most common for exam scenarios).
4. Set your time period (e.g., monthly) and budget amount (e.g., $20).
5. Choose what to include (all services, or filter by service, tag, or linked account).
6. Configure alerts:

• Example: Send an email when actual cost is > 80% of the budget.
• You can also alert based on forecasted cost (e.g., “You’re projected to exceed $20 this month”).

1. Review and create the budget.

When to use AWS Budgets:

• You want to be proactively notified before you overspend.
• You manage a student project with a strict monthly limit.
• Your startup wants email alerts if test environments cost more than expected.

Important nuance:

• Budgets do not automatically stop resources.

They notify you so humans (or automation you build) can respond.

For the exam, remember: Budgets = alerts and thresholds, not invoices or deep analysis.

Step 7 – Quick Check: Picking the Right Cost Tool

Test your understanding of Billing vs Cost Explorer vs Budgets.

Step 8 – AWS Pricing Calculator & TCO Tools (Conceptual View)

So far we focused on after you start using AWS. Now let’s look at before you deploy.

AWS Pricing Calculator

The AWS Pricing Calculator is a web-based tool that helps you estimate AWS costs in advance.

What you do with it:

• Build a hypothetical architecture (e.g., 2 EC2 instances, 1 RDS database, S3 storage, data transfer).
• Choose instance types, storage sizes, regions, and usage patterns.
• Get a monthly cost estimate.

When to use it:

• Planning a new workload and need a cost estimate for a proposal or assignment.
• Comparing cost of different designs (e.g., t3.micro vs t3.small; single-AZ vs Multi-AZ RDS).

TCO (Total Cost of Ownership) Concepts

Historically, AWS provided a dedicated TCO Calculator comparing on-premises vs AWS costs (hardware, power, cooling, staff). Today, AWS emphasizes TCO concepts and uses the Pricing Calculator plus whitepapers and guidance.

For CLF-C02-level understanding:

• TCO = the full, long-term cost of running a system (not just hardware):
• Servers, storage, networking
• Power, cooling, data center space
• Staff time (maintenance, upgrades)
• AWS helps reduce TCO by:
• Eliminating hardware purchase cycles
• Reducing over-provisioning
• Offloading infrastructure management to AWS

Exam framing:

• If a question asks about estimating future AWS costs for a design → AWS Pricing Calculator.
• If a question mentions comparing on-prem TCO vs AWS → think TCO analysis using AWS tools and guidance (historically TCO calculator, now often wrapped into broader cost tools and whitepapers).

Step 9 – AWS Support Plans: Overview and Key Differences

AWS offers four main Support plans (current as of early 2026):

1. Basic Support (included with all accounts)

• Cost: Free (included).
• Features:
• 24/7 access to customer service, billing support, and the AWS Support Center.
• Access to documentation, whitepapers, AWS Knowledge Center, and forums.
• No technical case support for troubleshooting workloads.

1. Developer Support

• For non-production or test environments.
• Cost: Starts at a low monthly fee (percentage of AWS usage with a minimum charge).
• Features (conceptual):
• Business-hours access to Cloud Support Associates via email.
• Guidance on best practices and use of core AWS services.
• Longer response times than Business/Enterprise.

1. Business Support

• For production workloads.
• Cost: Higher than Developer (percentage of usage with a higher minimum).
• Features:
• 24/7 access to Cloud Support Engineers by phone, chat, and email.
• Faster response times, including for production system impairments.
• Access to AWS Trusted Advisor full checks.
• Support for third-party software on AWS (e.g., OS, DBs, some apps).

1. Enterprise On-Ramp & Enterprise Support

(For CLF-C02, typically summarized as Enterprise-level support.)

• For mission-critical workloads.
• Features (conceptual):
• All Business Support features plus:
• Access to a pool of Technical Account Managers (TAMs) (On-Ramp) or a designated TAM (Enterprise).
• Proactive guidance, architectural reviews, and operations planning.
• Faster response times for critical issues.

Key exam distinctions:

• Basic: No technical support cases; only account & billing support + docs.
• Developer: For dev/test, email access to support, slower response.
• Business: For production, 24/7 phone/chat/email, full Trusted Advisor checks.
• Enterprise (incl. On-Ramp): For mission-critical, includes TAM support and proactive guidance.

You don’t need exact prices or SLAs, but you must know which plan fits which business need.

Step 10 – Match the Scenario to the AWS Support Plan

Choose the most appropriate Support plan for this scenario.

Step 11 – Flashcards: Core Tools and Support Plans

Use these flashcards to reinforce the most testable concepts.

Step 12 – Mini Scenario Drill: Choose the Right Tool or Plan

For each scenario, decide which tool or Support plan fits best. Jot down your choices, then compare with the suggested answers.

1. Scenario 1

Your professor wants to know how much your research project spent on S3 in the last 6 months, and whether the cost is trending up or down.

• Options: Billing console (Bills), Cost Explorer, AWS Budgets, AWS Pricing Calculator

1. Scenario 2

You’re planning a new architecture for a hackathon and want to estimate how much it will cost each month before you deploy anything.

• Options: Billing console, Cost Explorer, AWS Budgets, AWS Pricing Calculator

1. Scenario 3

Your student club wants an email if monthly AWS costs go above $15, so they can manually shut down some resources.

• Options: Billing console, Cost Explorer, AWS Budgets, AWS Pricing Calculator

1. Scenario 4

A hobbyist developer runs a non-production side project on AWS and wants basic technical guidance, but doesn’t need 24/7 phone support.

• Options: Basic, Developer, Business, Enterprise

---

Suggested answers:

1. Scenario 1 → Cost Explorer (trend over time + filter by S3).
2. Scenario 2 → AWS Pricing Calculator (pre-deployment estimate).
3. Scenario 3 → AWS Budgets (alert when cost exceeds threshold).
4. Scenario 4 → Developer Support (non-production, lower-cost technical support).