Free Tier and billing
Understand the 2025 Free plan and Paid plan, what is always free, how AWS bills you, where to see credits and costs, how cost allocation tags work, and the traps that turn a free lab into a bill.
Assumes: .NET 10 LTS ยท AWS SDK for .NET v4 (AWSSDK.CostExplorer 4.1.0.2, AWSSDK.FreeTier 4.1.0.2) ยท AWS CLI v2 ยท Region us-east-1. Verified against official sources on 2026-11-17.
Learning objectives
By the end of this lesson you can:
- Explain the Free plan and Paid plan introduced for accounts created on or after 2025-07-15, how credits work, and what happens when the Free plan ends.
- Tell the difference between always-free offers, short-term trials, credits and the legacy 12-month Free Tier.
- Find your plan state, remaining credits, bills and month-to-date cost in the console, the CLI and C#.
- Activate cost allocation tags (
Project,Lab) and group costs by them in Cost Explorer. - Name the AWS billing traps that catch learners and banks alike, and say how to detect each one.
Prerequisites
- Cost guardrails โ budgets, the billing alarm and Cost Anomaly Detection are already set up there; this lesson does not repeat them
- AWS accounts and Organizations and AWS CLI v2 with SSO profiles (you need the
learn-billingprofile) - Optional for the C# part: .NET 10 SDK
Why this matters in banking
In a bank, cloud cost is a control topic, not just a finance topic. Harbourline Bank's finance team must charge AWS spend back to products ("Payments", "Data Platform"), forecast it for the annual budget and explain every unusual spike to management. A risk team asks whether an unexpected cost could be a sign of compromise โ attackers who steal credentials often launch large compute fleets for crypto-mining. And a regulator asks whether the bank can exit a provider in an orderly way, which requires knowing what is running and what it costs.
At learner scale the same discipline protects your own wallet. Most "surprise AWS bill" stories come from resources that are billed by the hour while doing nothing: a NAT gateway left behind by a networking lab, a load balancer, a database, public IPv4 addresses. Knowing how billing works โ and how to see it โ is the cheapest insurance you will ever buy.
The idea in plain language
AWS bills you for what you use, measured by the second, hour, gigabyte or request, and sends one bill per month. There is no up-front licence fee; the flip side is that anything you leave running keeps counting.
Since 15 July 2025, a new AWS account chooses one of two plans at sign-up:
- Free plan โ you cannot be charged. You get USD 100 in credits at sign-up and can earn up to USD 100 more by completing guided activities. Only a selection of services is available. The plan ends after six months or when the credits are used up, whichever comes first. Then the account closes, unless you upgrade; AWS keeps your content for 90 days so you can still upgrade, then deletes it.
- Paid plan โ the same credits, all services, and normal pay-as-you-go billing once credits and free allowances are used. The account never closes on its own.
On both plans, always-free offers (over 30 services, each with a monthly limit, such as Lambda's one million requests) keep working. Paid plan accounts also get short-term trials of some services.
Analogy: The Free plan is a pre-paid travel card with a spending cap and an expiry date: when it runs out, it simply stops working. The Paid plan is a credit card that comes with a welcome voucher: the voucher is spent first, then the card keeps paying โ so you need spending alerts, because nothing stops it automatically.
In this course you are most likely on the Paid plan, because creating an AWS Organization (Path A in Module 0) automatically upgrades a Free plan account. That is why the guardrails from Module 0 are mandatory.
What problem the AWS service solves
| Tool | What it is | Why it exists | Limitations and sharp edges |
|---|---|---|---|
| Free Tier (plans, credits, always-free, trials) | Programmes that let you try AWS cheaply | Learning and evaluation without a bill | Credits are not unlimited and some expire; always-free limits are per month and per account/organisation; not every service is covered |
| Billing and Cost Management console | Home page, Bills, Payments, Credits, Free Tier, Cost Explorer, Budgets, Data Exports, Cost allocation tags | One place for cost visibility and controls | Data refreshes at least daily, not in real time. In an Organization most billing views live in the management account |
| AWS Cost Explorer | Interactive charts and an API for cost and usage | Find what costs money, by service, account, Region or tag | The UI is free; the API costs USD 0.01 per paginated request. Up to 13 months of history plus an 18-month forecast |
| Cost allocation tags | Tag keys (such as Project) activated for billing | Charge-back and "which lab is costing me?" | Must be activated; keys can take up to 24 hours to appear and up to 24 hours to activate; untagged resources show as an empty value |
| AWS Budgets / Cost Anomaly Detection | Alerts on thresholds and on unusual spend | Early warning | Alerts, not brakes (unless you configure budget actions). Already configured in Cost guardrails |
| AWS Data Exports (CUR 2.0) | Scheduled, detailed cost and usage files delivered to S3 | Line-item analysis with Athena, BI tools or FinOps platforms | You pay for the S3 storage and any queries; overkill for a single learner |
| AWS Pricing Calculator | Browser tool for estimates | Price a design before you build it | An estimate only; it does not know your discounts or real usage. Covered in Lab 1.4 |
| Consolidated billing | The Organizations feature where the management account pays for all member accounts | One bill, combined volume tiers, shared Savings Plans and RI discounts | Member-account bills are informational; the management account can reallocate discounts |
Free plan vs Paid plan in detail
Checked against the official Choosing a plan page on 2026-11-17:
| Free plan | Paid plan | |
|---|---|---|
| Sign-up credits | USD 100, plus up to USD 100 more from activities | Same |
| Services | A selection; excludes things that could drain credits fast or involve hardware, such as Savings Plans, Reserved Instances and some Marketplace offers | All services and features |
| Charges | None | Pay-as-you-go beyond credits and free allowances |
| Free offers active | Always free | Always free and short-term trials |
| End | After 6 months or when credits are used | Never closes on its own |
| At the end | Account closes; content kept 90 days; upgrade within that window to keep it; remaining credits then apply to future bills | โ |
| Other promotional credits | Not eligible | Eligible |
| Automatic upgrade triggers | Joining AWS Organizations, setting up a Control Tower landing zone, joining the AWS Partner Network, a Professional Services contract, an Enterprise Agreement, a Skill Builder Team subscription, or designating the account as HIPAA or SEC compliant | โ |
Credit expiry. AWS pages differ in wording: the Free Tier FAQ says Free plan credits must be used within the six-month plan, while service pricing pages (for example Secrets Manager) say credits must be used within 12 months of account creation. Treat the Credits page in your own Billing console as the source of truth โ VERIFY.
Older accounts: the legacy Free Tier
Accounts created before 15 July 2025 stay on the legacy Free Tier, which had three parts: 12-month free offers (for example, a small EC2 instance and some S3 storage for the first year), always-free offers and short-term trials. Every legacy account is now more than a year old, so its 12-month offers have ended; always-free offers and trials remain. If you read a blog post promising "750 free hours of EC2 for a year", it describes the legacy model.
What "always free" covers (examples)
Always-free limits reset on the first day of each month and do not roll over. Verified examples:
| Service | Always-free allowance (per month) | Note |
|---|---|---|
| AWS Lambda | 1 million requests and 400,000 GB-seconds of compute | Not for functions with Provisioned Concurrency |
| Amazon DynamoDB | 25 GB of storage (plus some capacity) | On-demand vs provisioned details differ โ VERIFY on the DynamoDB pricing page |
| Amazon CloudWatch | 10 custom metrics (plus other small allowances) | Logs ingestion and storage beyond the allowance are billed |
| AWS KMS | 20,000 requests | The key itself still costs USD 1 per month |
| Data transfer out to the internet | An always-free monthly allowance aggregated across services โ VERIFY the current amount | Beyond that, per-GB charges apply |
Amazon S3 storage is not listed as always free in the current model: on the Free plan it is paid for from credits.
Microsoft / Azure comparison
| You know (Microsoft/Azure) | AWS equivalent | What's different |
|---|---|---|
| Azure free account (credit for 30 days + 12 months of popular services + always free) | Free plan (credits, 6 months, account closes) or Paid plan | AWS's Free plan closes the account at the end instead of stopping resources; Azure asks you to upgrade |
| Azure Cost Management + Billing | AWS Billing and Cost Management console | Similar scope. Cost Explorer's UI is free; its API is charged per request |
| Azure cost analysis grouped by tag | Cost Explorer grouped by cost allocation tag | AWS tags must be activated for billing before they appear |
| Azure Budgets | AWS Budgets | Very similar; AWS adds a zero-spend template |
| Azure Advisor cost recommendations | Cost Optimization Hub, Compute Optimizer, Trusted Advisor | Several tools rather than one |
| Azure cost exports to a storage account | AWS Data Exports (CUR 2.0) to S3 | Query CUR with Athena (Module 7) |
| EA / MCA billing account with subscriptions underneath | Organization management account paying for member accounts (consolidated billing) | Volume tiers and commitment discounts are shared across the organization |
| Azure Pricing Calculator | AWS Pricing Calculator | Both are estimates only |
Architecture
How cost data flows in your Module 0 organisation, and who can see what:
Security-boundary view. Billing data reveals what a bank runs and how much it spends, so access is limited: the BillingViewer permission set (AWS managed policy AWSBillingReadOnlyAccess) can read bills, Cost Explorer, budgets and Free Tier state, but cannot change anything. Activating cost allocation tags or creating exports needs a write-capable role (learn-management). Remember from Module 0 that IAM roles see billing pages only because you activated IAM user and role access to Billing information as root.
Step-by-step implementation
Check your plan and credits
Sign in to the access portal โ management account โ BillingViewer โ Management console. Open Billing and Cost Management (search "Billing"). The home page shows your plan, remaining credits and, on the Free plan, the days left. Credits in the left menu lists each credit, its remaining balance and expiry date.
Look at Free Tier usage
Billing and Cost Management โ Free Tier lists each active offer, your month-to-date usage and a forecast. AWS emails the account's root address when a service passes 85% of its free limit. For a management account in an Organization these Free Tier alerts are not on by default: opt in under Preferences โ Billing preferences โ Alert preferences โ Edit โ Receive AWS Free Tier alerts. You can change the alert email address on the same page.
Read a bill
Bills shows charges per month, service and Region. Pick the current month and expand a service to see usage types such as USE1-NatGateway-Hours or USE1-PublicIPv4:InUseAddress. The prefix (USE1) is the Region. Charges covered by credits appear as a credit line, so a "USD 0.00 due" bill can still show usage you should understand.
Activate the course's cost allocation tags
Every lab tags resources Project=cea-lab, Lab=<lab-id>, Environment=learn, Owner=<you>. Those tags only appear in billing tools after activation in the management account. Switch to the ManagementAdmin role, then Billing and Cost Management โ Cost allocation tags โ User-defined cost allocation tags, select Project, Lab, Environment and Owner โ Activate. A key only appears in that list after a resource has carried it (allow up to 24 hours after the first tagged resource exists), and activation itself can take up to 24 hours. Activation applies from then on; the same page offers a separate backfill request to apply active tags to earlier months (how far back is โ VERIFY).
Group cost by Project in Cost Explorer
Cost Explorer โ date range "Month to date" โ Group by: Tag โ Project. You will see a cea-lab bar and a "No tag key: Project" bar. Anything in the second bar is spend you cannot attribute โ in a bank, that is the first thing FinOps chases.
Optional: check the same from the CLI and C#
Use the commands in the AWS CLI section and the program in Complete code. Free Tier API calls are free; each Cost Explorer API request costs USD 0.01.
AWS Console instructions
Navigation summary (menu names checked 2026-11-17; no screenshots):
- Plan, credits, days remaining: Billing and Cost Management โ Home, and Credits
- Free Tier usage: Billing and Cost Management โ Free Tier
- Free Tier alert opt-in and email: Billing and Cost Management โ Preferences โ Billing preferences โ Alert preferences
- Upgrade a Free plan account: Billing and Cost Management โ Upgrade plan (or the banner on the console home page)
- Monthly bills: Billing and Cost Management โ Bills
- Cost analysis: Billing and Cost Management โ Cost Explorer
- Tags for billing: Billing and Cost Management โ Cost allocation tags
- Detailed exports: Billing and Cost Management โ Data Exports
- Budgets and anomalies: see Cost guardrails
AWS CLI
Billing APIs are global and answered from us-east-1. Use the learn-billing profile (read-only) unless a command says otherwise.
# Sign in once for all profiles that share the 'cea' SSO session
aws sso login --sso-session cea
# Plan type (FREE or PAID), status (NOT_STARTED, ACTIVE, EXPIRED), credits left, expiry. Free of charge.
aws freetier get-account-plan-state --profile learn-billing --region us-east-1
# Month-to-date usage against each Free Tier offer, as a table
aws freetier get-free-tier-usage --profile learn-billing --region us-east-1 `
--query "freeTierUsages[].{Service:service,Usage:usageType,Actual:actualUsageAmount,Limit:limit,Forecast:forecastedUsageAmount}" `
--output table
# Month-to-date cost grouped by the Project tag (USD 0.01 per request)
aws ce get-cost-and-usage --profile learn-billing --region us-east-1 `
--time-period Start=2026-11-01,End=2026-11-17 `
--granularity MONTHLY `
--metrics UnblendedCost `
--group-by Type=TAG,Key=Project `
--query "ResultsByTime[].Groups[].{Tag:Keys[0],USD:Metrics.UnblendedCost.Amount}" `
--output table
# Which tag keys exist and whether they are active (USD 0.01 per request)
aws ce list-cost-allocation-tags --type UserDefined --profile learn-billing --region us-east-1
# Activate the course tag keys: needs a write role in the management account (USD 0.01)
aws ce update-cost-allocation-tags-status --profile learn-management --region us-east-1 `
--cost-allocation-tags-status TagKey=Project,Status=Active TagKey=Lab,Status=Active TagKey=Environment,Status=Active TagKey=Owner,Status=ActiveHow to read these:
get-account-plan-statereturnsaccountPlanType,accountPlanStatus,accountPlanRemainingCreditsandaccountPlanExpirationDate. On Path A you will seePAID.- In
get-free-tier-usage, the field names in the--queryfollow the API's camelCase response โ VERIFY against your CLI output (run it once without--queryto see the shape). - In
get-cost-and-usage,Endis exclusive; group keys come back asProject$cea-lab, and an empty value after$means "untagged".
Infrastructure as Code
Two things belong in code: tagging everything by default and activating the tag keys.
terraform {
required_providers {
aws = {
source = "hashicorp/aws"
version = "~> 6.0"
}
}
}
# Workload provider: every resource it creates gets the course tags automatically.
provider "aws" {
region = "us-east-1"
profile = "learn-sandbox"
default_tags {
tags = {
Project = "cea-lab"
Lab = "m01-hello-aws"
Environment = "learn"
Owner = "alex.learner"
}
}
}
# Billing provider: cost allocation tags are activated in the management (payer) account.
provider "aws" {
alias = "billing"
region = "us-east-1"
profile = "learn-management"
}
resource "aws_ce_cost_allocation_tag" "course" {
for_each = toset(["Project", "Lab", "Environment", "Owner"])
provider = aws.billing
tag_key = each.value
status = "Active"
}aws_ce_cost_allocation_tag fails if the key has never been seen on any resource yet โ create one tagged resource first, wait for the key to appear, then apply.
Complete code
A small .NET 10 console app that prints your plan state and month-to-date cost per Project tag value. It compiles against the packages below (checked in a .NET 10 SDK container on 2026-11-17).
<Project Sdk="Microsoft.NET.Sdk">
<PropertyGroup>
<OutputType>Exe</OutputType>
<TargetFramework>net10.0</TargetFramework>
<Nullable>enable</Nullable>
<ImplicitUsings>enable</ImplicitUsings>
<TreatWarningsAsErrors>true</TreatWarningsAsErrors>
<RootNamespace>Harbourline.Billing.Snapshot</RootNamespace>
<InvariantGlobalization>true</InvariantGlobalization>
</PropertyGroup>
<ItemGroup>
<PackageReference Include="AWSSDK.CostExplorer" Version="4.1.0.2" />
<PackageReference Include="AWSSDK.FreeTier" Version="4.1.0.2" />
<!-- Needed at runtime so IAM Identity Center (SSO) profiles resolve -->
<PackageReference Include="AWSSDK.SSO" Version="4.1.0.2" />
<PackageReference Include="AWSSDK.SSOOIDC" Version="4.1.0.2" />
</ItemGroup>
</Project>// Billing snapshot: Free Tier plan state + this month's cost grouped by the Project tag.
// Run with a read-only billing profile, e.g.: dotnet run -- learn-billing
using System.Globalization;
using Amazon;
using Amazon.CostExplorer;
using Amazon.CostExplorer.Model;
using Amazon.FreeTier;
using Amazon.FreeTier.Model;
using Amazon.Runtime.CredentialManagement;
var profileName = args.Length > 0 ? args[0] : "learn-billing";
// Resolve the SSO profile from %USERPROFILE%\.aws\config (sign in first with: aws sso login).
var chain = new CredentialProfileStoreChain();
if (!chain.TryGetAWSCredentials(profileName, out var credentials))
{
Console.Error.WriteLine($"Profile '{profileName}' not found or unusable. Run: aws configure sso");
return 2;
}
// Billing APIs are served from us-east-1, whatever Region your workloads use.
var billingRegion = RegionEndpoint.USEast1;
// 1. Free Tier plan state (free of charge).
using (var freeTier = new AmazonFreeTierClient(credentials, billingRegion))
{
var plan = await freeTier.GetAccountPlanStateAsync(new GetAccountPlanStateRequest());
Console.WriteLine($"Account plan : {plan.AccountPlanType} ({plan.AccountPlanStatus})");
Console.WriteLine($"Credits left : {plan.AccountPlanRemainingCredits?.Amount} {plan.AccountPlanRemainingCredits?.Unit}");
Console.WriteLine($"Plan expires : {plan.AccountPlanExpirationDate}");
}
// 2. Month-to-date unblended cost by Project tag (each Cost Explorer API request costs USD 0.01).
var today = DateTime.UtcNow.Date;
var monthStart = new DateTime(today.Year, today.Month, 1, 0, 0, 0, DateTimeKind.Utc);
var end = today == monthStart ? today.AddDays(1) : today; // End is exclusive and must be after Start
using var ce = new AmazonCostExplorerClient(credentials, billingRegion);
var response = await ce.GetCostAndUsageAsync(new GetCostAndUsageRequest
{
TimePeriod = new DateInterval
{
Start = monthStart.ToString("yyyy-MM-dd", CultureInfo.InvariantCulture),
End = end.ToString("yyyy-MM-dd", CultureInfo.InvariantCulture),
},
Granularity = Granularity.MONTHLY,
Metrics = ["UnblendedCost"],
GroupBy = [new GroupDefinition { Type = GroupDefinitionType.TAG, Key = "Project" }],
});
foreach (var period in response.ResultsByTime ?? [])
{
Console.WriteLine($"Period {period.TimePeriod?.Start} to {period.TimePeriod?.End}");
foreach (var group in period.Groups ?? [])
{
// Tag groups come back as "Project$cea-lab"; an empty value means "untagged".
var key = group.Keys?.FirstOrDefault() ?? "(none)";
var cost = group.Metrics?.GetValueOrDefault("UnblendedCost");
var amount = decimal.Parse(cost?.Amount ?? "0", CultureInfo.InvariantCulture); // money is decimal, never double
Console.WriteLine($" {key,-30} {amount,12:N2} {cost?.Unit}");
}
}
return 0;Run it:
aws sso login --sso-session cea
dotnet run -- learn-billingExample output (fictional):
Account plan : PAID (ACTIVE)
Credits left : 182.37 USD
Plan expires :
Period 2026-11-01 to 2026-11-17
Project$ 0.00 USD
Project$cea-lab 0.04 USDCode explained line by line
using Amazon.CostExplorer;/using Amazon.FreeTier;โ the clients from theAWSSDK.CostExplorerandAWSSDK.FreeTierv4 packages.AWSSDK.SSOandAWSSDK.SSOOIDCin the project file โ the SDK loads them at runtime to turn ansso_sessionprofile into credentials. Without them the app compiles but fails when the profile is used.new CredentialProfileStoreChain()andTryGetAWSCredentials(profileName, ...)โ read%USERPROFILE%\.aws\configand build credentials for the named profile, the same pattern as the Module 0 verify-setup lab. SDK for .NET: first contact explains the full credential chain.RegionEndpoint.USEast1โ billing, Cost Explorer and Free Tier APIs are global services answered from us-east-1, even if your workloads run in eu-west-2.GetAccountPlanStateAsyncโ returns plan type, status, remaining credits and expiry. The?.operators handle fields that are absent (for example no expiry on a Paid plan).monthStart/endโ Cost Explorer dates areyyyy-MM-ddstrings andEndis exclusive, so on the first day of a month we use tomorrow to keep the range valid.Granularity.MONTHLY,Metrics = ["UnblendedCost"]โ one total per month, using the rate actually charged to each line item. (AmortizedCostspreads up-front commitments; you meet it in Pricing models.)GroupDefinitionType.TAG, Key = "Project"โ split costs by theProjectcost allocation tag. It works only after the tag key is activated.response.ResultsByTime ?? []โ in SDK for .NET v4, empty collections in responses can benull, so we default to an empty list.decimal.Parse(cost?.Amount ?? "0", CultureInfo.InvariantCulture)โ Cost Explorer returns amounts as strings; we parse them asdecimalwith the invariant culture so0.04is not misread on a machine set to a comma-decimal locale. Money is neverdoublein this course.
Security considerations
- Read-only by default. Use
learn-billing(AWSBillingReadOnlyAccess) for looking; switch tolearn-managementonly to activate tags or change preferences. - Billing data is confidential business information. Do not paste bills or Cost Explorer exports into public places or AI tools without removing account IDs.
- Cost spikes can be security events. A sudden EC2 or GPU spend in an unused Region is a classic sign of stolen credentials. Cost Anomaly Detection (Module 0) and GuardDuty (Module 5) work together here.
- Tags are not access control by themselves. Anyone who can tag resources can change charge-back; banks restrict tag edits with tag policies and SCPs (Module 15).
โ Learning shortcut โ not for production
You look at billing for a single small organisation through the console and an occasional API call. A bank runs a FinOps practice: CUR 2.0 exports into a central data account, Athena or a BI dashboard per product, enforced tag policies with required keys, monthly cost reviews with product owners, commitment purchases (Savings Plans) approved by finance, and budget actions that notify or restrict. Module 15 builds that version.
โ Learning shortcut โ not for production
Relying on the Free plan's "cannot be charged" guarantee is fine for a personal sandbox, but the account closes after six months. Never put anything you need to keep โ a Terraform state bucket, a demo for an interview โ in an account that might close. In real organisations every account is on standard billing with budgets and alerts.
Banking use case
Harbourline Bank tags every resource with CostCentre, Product (for example payments, data-platform), Environment and DataClassification, enforced by a tag policy. The management account exports CUR 2.0 daily into a FinOps data account; a weekly Athena query lists the top ten cost increases per product, and a Quick Sight dashboard shows month-to-date spend against budget. Cost Anomaly Detection monitors each product and routes alerts to that team's channel. When the Payments team sees NAT gateway data-processing charges triple after a release, the investigation finds a new service calling S3 through the NAT gateway instead of a VPC gateway endpoint โ a cost fix that also improves the security posture (Module 2). The bank's finance and procurement teams, not engineers, decide on commitments such as Savings Plans.
Common mistakes
- Assuming "Free Tier" means everything is free โ the term covers several programmes โ read the plan, check the Free Tier page, and keep budgets on.
- Forgetting that creating an Organization upgrades a Free plan account โ the guarantee of zero charges disappears โ set budgets first (Module 0 does).
- Expecting tags to show up in Cost Explorer immediately โ activation is a separate step with up to a day of delay โ activate once, early.
- Calling the Cost Explorer API in a tight loop โ USD 0.01 per request adds up in scripts and dashboards โ cache results; the data only refreshes about daily anyway.
- Looking for the bill in the sandbox account โ consolidated billing puts it in the management account โ use
learn-billing. - Deleting a stack but not what it left behind โ snapshots, log groups, Elastic IPs and KMS keys often survive โ run the teardown checklist.
- Using
doublefor amounts in reports โ rounding errors โ parse amounts asdecimal.
The cost traps you will meet
Prices are us-east-1 list prices checked on the official pricing pages on 2026-11-17; they change, so re-check before you rely on them.
| Trap | What it costs | How to find it | How to avoid it |
|---|---|---|---|
| NAT gateway left running | About USD 0.045 per hour (โ USD 32 per month) plus USD 0.045 per GB processed โ the official example uses US East (Ohio); us-east-1 is the same at the time of writing โ VERIFY | Bills โ VPC โ NatGateway-Hours | Delete after networking labs; use VPC endpoints for S3/DynamoDB |
| Idle Application Load Balancer | USD 0.0225 per hour (โ USD 16 per month) plus LCU charges | Bills โ Elastic Load Balancing | Delete with the stack; no traffic does not mean no charge |
| Public IPv4 addresses | USD 0.005 per hour each, in use or idle (โ USD 3.65 per month) | Bills โ VPC โ PublicIPv4:InUseAddress / IdleAddress | Release Elastic IPs; avoid public IPs on instances; prefer private subnets |
| KMS customer managed keys | USD 1 per key per month, prorated hourly | KMS console โ Customer managed keys | Schedule deletion when a lab ends โ keys pending deletion are not charged |
| Secrets Manager secrets | USD 0.40 per secret per month plus USD 0.05 per 10,000 API calls | Secrets Manager console | Delete lab secrets (they have a recovery window) |
| CloudWatch Logs without retention | Storage keeps growing; new log groups default to never expire | CloudWatch โ Log groups โ Retention column | Set retention (for example 7 days in labs) in IaC |
| EBS volumes and snapshots | Storage per GB-month, even when the instance is gone | EC2 โ Volumes (state available) and Snapshots | Delete with the instance; check snapshot lists |
| RDS instances | Hourly while running; stopped instances restart automatically after 7 days โ VERIFY | RDS console | Delete with a final snapshot only if needed |
| Data transfer out | Per GB beyond the free allowance; cross-AZ and cross-Region traffic is also charged | Cost Explorer โ group by Usage type | Keep labs small; watch downloads from S3 |
| Forgotten Regions | Anything above, in a Region you never look at | Cost Explorer โ group by Region; Module 0's SCP blocks most Regions | Stick to us-east-1 / eu-west-2 |
| Cost Explorer API | USD 0.01 per request | Bills โ Cost Explorer | Use the console for browsing |
Troubleshooting
| Symptom | Likely cause | Fix |
|---|---|---|
| "You don't have permission" on Billing pages | IAM access to billing not activated, or wrong profile | Root once: Account โ IAM user and role access to Billing information โ Activate. Use learn-billing |
AccessDeniedException on ce:GetCostAndUsage from the sandbox profile | Member account, or no Cost Explorer permission | Use learn-billing in the management account |
| Free Tier page shows no data | Organization member account, expired offers, or a management account that has not opted in to alerts | Check from the management account; opt in under Billing preferences |
| Tag key not listed under Cost allocation tags | No resource has carried the tag yet, or less than 24 hours have passed | Create a tagged resource; wait; refresh |
| Cost Explorer shows "No tag key: Project" for everything | Tag key not activated, or resources untagged | Activate the key; fix tagging in IaC (default_tags / Tags.Of) |
ValidationException about the time period | End not after Start, or wrong date format | Use yyyy-MM-dd; End is exclusive |
| Bill shows charges although credits remain | Service not eligible for credits, or charge outside credit terms | Open the line item; check the Credits page for applicable products |
| Account suddenly closed | Free plan ended (6 months or credits used) | Upgrade within 90 days from the console sign-in page to recover content |
aws freetier is not a valid choice | Old CLI | Update AWS CLI v2 |
Cost and cleanup
Cost: $0 for the console steps. Optional API calls: Free Tier API calls are free; each Cost Explorer request (get-cost-and-usage, list-cost-allocation-tags, update-cost-allocation-tags-status) costs USD 0.01, so doing every CLI and C# step once costs about USD 0.05. Activating cost allocation tags is free.
Cleanup: nothing to delete โ this lesson only reads data and changes a billing setting you want to keep. End with the standard check that no lab resources remain:
aws resourcegroupstaggingapi get-resources --tag-filters Key=Project,Values=cea-lab `
--query "ResourceTagMappingList[].ResourceARN" --profile learn-sandbox --region us-east-1
aws sso logoutAn empty list ([]) means nothing tagged for the course is left in us-east-1. Repeat with --region eu-west-2 if you used London.
Exercises
- ๐ข Guided: Find your plan type, remaining credits and their expiry in the console, then confirm the same with
aws freetier get-account-plan-state. Activate theProject,Lab,EnvironmentandOwnertag keys (or note that they are not listed yet and come back after the Hello AWS lab). - ๐ก Challenge: After you have run the Hello AWS lab, use Cost Explorer (console) to show this month's cost grouped by Tag: Lab, filtered to Tag: Project = cea-lab. Then reproduce it with one
aws ce get-cost-and-usagecommand that uses--filter. - ๐ด Live problem: On the 9th of the month your billing alarm fires at USD 8. Cost Explorer shows "Amazon Virtual Private Cloud" as the top service and nothing tagged
cea-lab. You finished the networking lab last week and "deleted the stack". Find out what is running, why it was not tagged, and what you will change so it cannot happen again.
Assignment
Write docs/cost-baseline.md in your learning repository: your plan type and credit expiry (no account IDs), the four activated tag keys, a table of the ten cost traps above with how you will detect each, and the output of BillingSnapshot with the account details removed. Commit the C# project under tools/billing-snapshot/.
Solutions
On Path A you should see PAID / ACTIVE and your remaining credits on both the Billing home page and from get-account-plan-state. If Project is not yet in the Cost allocation tags list, that is expected: AWS only lists keys after a tagged resource has existed, so return after the lab. Why: activation is per key, in the payer account, and only for keys AWS has seen.
aws ce get-cost-and-usage --profile learn-billing --region us-east-1 `
--time-period Start=2026-11-01,End=2026-11-17 `
--granularity MONTHLY --metrics UnblendedCost `
--group-by Type=TAG,Key=Lab `
--filter file://project-filter.json{ "Tags": { "Key": "Project", "Values": ["cea-lab"] } }Putting the filter in a file avoids PowerShell's awkward JSON quoting. The result has one group per Lab$<lab-id> value. Why: filter narrows the data set (only course resources), group-by splits what remains (per lab) โ the same idea as WHERE versus GROUP BY in SQL.
In Cost Explorer, group by Usage type: NatGateway-Hours and possibly PublicIPv4:InUseAddress will dominate. Group by Region to find where. In the VPC console of that Region, list NAT gateways and Elastic IPs. Likely causes: the stack deletion failed part-way (check CloudFormation for DELETE_FAILED), or the NAT gateway was created by hand or by a different tool outside the stack, so it had no tags. Delete the NAT gateway, then release its Elastic IP (the IP keeps charging after the gateway is gone). Prevent it: tag through default_tags / Tags.Of(app) so every resource is tagged; run the teardown check by Region; consider a Budgets alert scoped to the VPC service. Why: hourly-billed networking resources are the classic trap because they cost money while carrying no traffic.
Knowledge check
Answer: The Free plan ends (it ends at six months or when credits run out, whichever is first). The account closes; AWS keeps the content for 90 days, during which you can upgrade to the Paid plan to regain access.
Answer: Always-free offers are monthly usage allowances on specific services that reset every month and do not expire with the plan; credits are a money balance that pays for eligible usage and is used up or expires. Always-free applies on both plans; short-term trials only on the Paid plan.
Answer: User-defined tags must be activated as cost allocation tags in the management account. A key appears for activation only after resources carry it (up to 24 hours), and activation can take up to another 24 hours.
Answer: The console UI is free. The API costs USD 0.01 per paginated request.
Answer: The management (payer) account, through consolidated billing. Member-account bills are informational.
Interview questions
- "How would you attribute AWS costs to products in a bank?" โ Mandatory tags enforced by tag policies and IaC defaults, activated as cost allocation tags; account-per-product-and-environment where possible (accounts are the cleanest cost boundary); CUR 2.0 exports analysed with Athena or a FinOps tool; regular reviews with product owners.
- "Your AWS bill jumped 40% this month. Walk me through the investigation." โ Cost Explorer by service, then usage type, Region, account and tag; compare with the previous period; check anomalies and recent deployments; check for security causes (new Regions, unusual instance types); fix, then add a guardrail (budget, SCP, IaC change).
- "What are the cost risks of a typical three-tier VPC lab?" โ NAT gateways, load balancers, public IPv4 addresses, databases and log retention; all billed by the hour or GB regardless of traffic.
- "What changed in the AWS Free Tier in 2025?" โ New accounts choose a Free plan (credits, six months, no charges, account closes at the end) or a Paid plan (same credits, all services, pay-as-you-go); always-free offers continue; older accounts stay on the legacy model.
Certification practice
A company wants to see AWS costs per project in AWS Cost Explorer. Resources are already tagged with a Project key. What must it do next?
A. Enable AWS Trusted Advisor
B. Activate Project as a user-defined cost allocation tag in the management account
C. Create an AWS Budget for each project
D. Purchase a Savings Plan
Answer: B. Tags appear in billing tools only after activation. A gives recommendations, not cost grouping. C creates alerts but does not make the tag visible in Cost Explorer. D is a pricing commitment, unrelated to reporting.
Which TWO are benefits of consolidated billing in AWS Organizations? (Choose two.)
A. One bill for multiple accounts B. Automatic encryption of all member-account data C. Combined usage across accounts for volume pricing tiers D. Free AWS Enterprise Support E. Removal of all data transfer charges
Answer: A and C. Consolidated billing gives one bill and aggregates usage so volume tiers and commitment discounts are shared. B, D and E are not features of consolidated billing.
A learner wants to explore AWS for three months with a guarantee that no charges can occur. Which choice meets this requirement?
A. Paid plan with a zero-spend budget B. Free plan C. Paid plan with Cost Anomaly Detection D. Legacy 12-month Free Tier
Answer: B. Only the Free plan prevents charges; its six-month limit covers three months. A and C alert but do not block charges. D is not available to new accounts created after 2025-07-15.
A team deletes its test EC2 instances every evening but the bill keeps rising. Cost Explorer shows charges for NatGateway-Hours and PublicIPv4:IdleAddress. What is the most cost-effective fix?
A. Buy a Compute Savings Plan B. Delete the NAT gateways and release unused Elastic IP addresses when the environment is not in use, and use VPC gateway endpoints for S3 access C. Move the instances to Spot D. Enable S3 Intelligent-Tiering
Answer: B. NAT gateways and idle public IPv4 addresses are billed hourly regardless of instances. A and C reduce compute cost, which is not the problem. D affects S3 storage classes only.
Completion checklist
- I know my plan type, remaining credits and when they expire
- Free Tier alerts reach me (opted in for the management account)
-
Project,Lab,EnvironmentandOwnerare activated cost allocation tags (or I know why they are not listed yet) - I can group month-to-date cost by
Projectin Cost Explorer - I ran
aws freetier get-account-plan-stateand, optionally, the C# billing snapshot - I can name five hourly-billed traps and how to find them
Key takeaways
- New accounts (from 2025-07-15) choose a Free plan (no charges, six months, closes at the end) or a Paid plan (same credits, pay-as-you-go); creating an Organization upgrades a Free plan account.
- Always-free allowances continue on both plans; legacy 12-month offers belong to older accounts.
- Billing lives in the management account; use a read-only billing profile to look and a write role only to change settings.
- Tags become useful for cost only after activation as cost allocation tags.
- The expensive surprises are resources billed by the hour while idle: NAT gateways, load balancers, public IPv4 addresses, databases, KMS keys and unexpired logs.
Further reading
- Choosing a plan (Free plan and Paid plan)
- Tracking your AWS Free Tier usage
- AWS Free Tier API operations
- AWS Free Tier and Legacy AWS Free Tier FAQs
- Analyzing your costs with AWS Cost Explorer and Cost Explorer pricing
- Activating user-defined cost allocation tags
- Consolidating billing for AWS Organizations
- What is AWS Data Exports?
- AWS managed policy AWSBillingReadOnlyAccess
- Pricing pages: Amazon VPC, Elastic Load Balancing, AWS KMS, Secrets Manager, AWS Lambda
Independent learning resource โ not affiliated with, endorsed or sponsored by Amazon Web Services. AWS and related marks are trademarks of Amazon.com, Inc. or its affiliates. All banking data in examples is fictional. Sample architectures are for learning and are not automatically compliant with GDPR, PCI DSS or any banking regulation.
AWS SDK for .NET: first contact
Call AWS from C# with the AWS SDK for .NET v4: how the SDK finds credentials and a Region, how SSO profiles work from code, how to register clients with dependency injection, and how to read the errors you will meet on day one.
Pricing models: On-Demand, Savings Plans, Reserved Instances and Spot
Choose the right way to pay for AWS compute and databases for each kind of banking workload, and look up real prices from the console, the CLI and C#.