Understanding Your AWS Account

Lesson purpose

An AWS account is both a technical boundary and a financial boundary. This lesson teaches a repeatable cost-control loop: estimate before deploying, monitor actual and forecast spend, allocate usage to owners, and optimize only after identifying the driver. It incorporates current Free Tier behavior and the pricing, quota, billing, budget, tagging, and organization concepts from uCertify Lesson 2, sections 2.1–2.6, and the Lesson 2 Modern deck.

Learning objectives

• Explain the current and legacy Free Tier models and build safe usage guardrails.
• Calculate an estimate from quantity, unit rate, duration, and secondary charges.
• Choose among On-Demand, Savings Plans/Reserved, Spot, and dedicated options using workload characteristics.
• Use the Pricing Calculator, service quotas, Billing, Budgets, Cost Explorer, and detailed exports.
• Distinguish resource tags from cost allocation tags and explain consolidated billing.
• Diagnose a cost change before changing architecture or purchasing commitments.

1. The cost-control loop

Teach the sequence as estimate → monitor → allocate → optimize. An estimate is a set of assumptions, not a promise. Monitoring compares actual and forecast cost with that estimate. Allocation connects spend to an account, service, Region, project, or owner. Optimization changes usage, configuration, purchase model, or architecture only after the largest driver is understood. A budget alert is useful only when a person or automation can investigate it.

2. Free Tier: current and legacy accounts

Older accounts created before July 15, 2025 may remain on the legacy program with service-specific offers, including older 12-month examples found in some study material. New customers use the current credits-based experience: a $100 sign-up credit and the possibility of additional credits, with a Free Plan that lasts up to six months or until credits are exhausted. Always-free offers may continue after the plan ends. Students must check the account’s actual plan and current AWS terms rather than memorizing a dated dollar or hour limit.

Free usage still needs guardrails. Confirm the plan, watch credits and usage, set actual and forecast budget alerts, and clean up compute, storage, snapshots, public addresses, and other lab resources. “Free Tier” does not mean every related resource is free, and a free service can still create charges for requests, transfer, logs, or dependent services.

3. Pricing is quantity × unit rate × duration

• Quantity: instances, GB-months, requests, messages, or provisioned units.
• Unit rate: price per unit varies by service, Region, tier, operating system, and purchase model.
• Duration: seconds, hours, months, or retention period.
• Secondary charges: data transfer, storage requests, snapshots, support, and taxes.

Service	Primary driver	Commonly missed driver
EC2	Instance family, operating system, and time	EBS, public IPv4, and data transfer
S3	Storage class and capacity	Requests, retrieval, and transfer
Lambda	Requests and execution duration	Logs and downstream services
RDS	Instance, storage, and deployment	Backups and transfer

A useful estimate records the Region, normal and peak usage, retention, and what is intentionally excluded. Change one assumption at a time so students can explain why totals differ.

4. Purchase options and the Pricing Calculator

On-Demand has no long commitment and fits uncertain or short-lived demand. Savings Plans and Reserved Instances lower the effective rate in exchange for a usage commitment; they are appropriate only when the baseline is understood. Spot uses spare capacity at a discount but can be interrupted, so it belongs with fault-tolerant or restartable work. Dedicated options address isolated hardware, licensing, or compliance requirements and usually cost more.

For the EC2/EBS lab, select a Region, operating system, instance family, hours, count, EBS type, size, performance, and snapshot assumptions. Compare an On-Demand design with a commitment option and identify the largest cost driver. For a multi-service estimate, add compute, storage, and transfer, record normal and peak scenarios, duplicate the estimate, change one design decision, and export both the totals and assumptions. The value of the calculator is transparency, not false precision.

5. Service quotas protect the account

A quota is an allowance on resources or API activity for an account and Region. Distinguish the default quota from the applied quota after an approved change. Adjustable quotas can sometimes be increased; nonadjustable quotas require a different architecture, account distribution, or service choice. Before a launch, view the applied quota, compare it with planned usage, request an increase with context, and track the request because approval can be partial or delayed. A quota is not a budget: a workload can stay under quota and still spend too much.

6. Billing, Budgets, Cost Explorer, and exports

Billing views answer different questions. Bills show charges by service, Region, linked account, and usage type. Payments show invoices, credits, payment methods, and transaction history. Tax settings hold legal registration information. Billing permissions should be granted deliberately; routine administration should not use the root user.

AWS Budgets turn thresholds into notifications. Use cost budgets for actual or forecast spend, usage budgets for a service or usage type, and commitment budgets for Savings Plans or Reserved Instance coverage and utilization. Scope a budget to the account, service, Region, tag, or other filter; set realistic thresholds; and notify people who can act. Cost Explorer explains the driver behind a change by comparing time ranges and grouping by service, Region, account, or tag. Detailed billing exports and the Cost and Usage Report support deeper analysis and external reporting.

7. Tags, cost allocation, and Organizations

A resource tag is metadata attached to a resource. A cost allocation tag is a tag activated for billing analysis. The same key can be present on a resource but absent from cost reports until it is activated, and not every charge maps neatly to one resource. Use a naming strategy that includes environment, application, owner, and cost center, but do not put secrets in tags.

AWS Organizations provides a management hierarchy and consolidated billing. Linked accounts keep workload boundaries while the management account receives the consolidated invoice and can use shared pricing benefits. Consolidation improves visibility and governance; it does not make ownership disappear. Account, Region, service, and tags should all support a clear answer to “who owns this spend?”

Classroom application

Have each group inspect a hypothetical flash-sale estimate and identify one assumption, one alert, one quota risk, and one owner. Then ask them to explain whether a price difference came from quantity, rate, duration, purchase commitment, or a secondary charge. End with a cleanup checklist and a screenshot or exported estimate as evidence.

Common misconceptions

• Free Tier means no bill is possible. Dependent services, overages, and plan changes can still create charges.
• The calculator is an invoice. It is an estimate whose assumptions must be verified.
• A quota increase is guaranteed. Requests can be delayed, limited, or denied.
• Tags automatically appear in cost reports. Cost allocation tags must be activated and used consistently.
• Consolidated billing means every account is interchangeable. Account boundaries, permissions, and ownership still matter.

Lesson summary

Account economics is an operational discipline. Estimate the workload, monitor the result, allocate responsibility, and optimize the measured driver. Current Free Tier rules require checking the account’s plan; pricing requires explicit dimensions; quotas protect service capacity; budgets and Cost Explorer turn signals into action; and tags plus Organizations make responsibility visible. The next lesson asks where to get authoritative help and how to match support capability to operational risk.