Topic lessonTopic: Costs, Free Tier and budgets
AWS pricing basics: estimate compute, storage and networking separately
An instance price is not the price of an entire system. Identify resources, billing units, quantities and purchase terms, then account for compute, storage and networking. Learn to identify omissions and explain differences from billing details without relying on fixed unit prices.
List a small design’s cost dimensions and assumptions, and distinguish an estimate from metered usage and billing.
Know that a Region is an AWS location, EC2 provides compute, and EBS provides block storage used with EC2. No real billing data is required.
Turn the design into a cost inventory
- Compute → Estimate scopeInclude compute dimensions.
- Storage → Estimate scopeAccount separately for storage.
- Network services → Estimate scopeInclude network and surrounding services; the lines do not describe packet flow.
- Compute
- Review count, OS, configuration, runtime and purchase option.
- Storage
- Review provisioned EBS capacity/performance, S3 storage and snapshots.
- Network services
- Review IPs, NAT, data transfer and other used services.
- Estimate scope
- Review all five dimensions in the next table and retain explicit exclusions.
Two similar apps can have different storage, transfer and runtime. EBS volume pricing includes provisioned capacity rather than only the files currently stored. Deleting some files does not necessarily shrink the provisioned-capacity bill proportionally.
Align units and assumptions before comparing rates
| Dimension | Quantity or condition | Example omission |
|---|---|---|
| Compute | Region, instance type, OS, count, runtime, purchase option and billing unit | Treating the server hourly rate as the price of the whole system |
| Storage | Provisioned EBS capacity/performance, S3 class/amount/duration and snapshots | Assuming stopped compute means storage charges have ended |
| Transfer and processing | Source, destination, direction, AZ/Region and NAT time/processing | Assuming a transfer price includes every NAT processing charge |
| Requests | GET, PUT or other request types and counts in the pricing table’s units | Counting stored data but omitting read/write requests |
| Logs | Ingested amount, stored amount/duration and queried data under feature-specific terms | Assuming ingestion includes all storage and querying |
| Comparison conditions | Equivalent period, scope and currency; tax, discounts, credits and allowances | Replacing unknown items with zero and calling an estimate a final bill |
A request asks a service to perform an operation. An S3 GET reads a stored object, such as file data. A log records events. Ingestion accepts logs into a logging service; storage and querying are separate uses. When accounting for log storage separately, do not count the same storage charge twice.
Worked example: separate included and unestimated costs
| Included item | Stipulated quantity | Invented rate | Cost |
|---|---|---|---|
| Compute | 1 instance × 10 hours = 10 instance-hours | $0.10 / instance-hour | $1.00 |
| Selected S3 storage | 2 GB-month | $0.05 / GB-month | $0.10 |
| Covered transfer | 3 GB | $0.20 / GB | $0.60 |
| Selected S3 GET requests | 2,000 = 2 × 1,000 requests | $0.03 / 1,000 requests | $0.06 |
| Log ingestion only | 1 GB | $0.50 / GB | $0.50 |
| Selected five-row subtotal | Sum money, not incompatible quantities | — | $2.26 |
Choose an option to see the result and explanation.
The next question is a separate case: consider storage resources after stopping EC2 at one hour.
Choose an option to see the result and explanation.
Explain differences from actual charges
- Align period, account scope, currency and cost metric.
- Find service/Region lines that differ from the estimate.
- Investigate count, runtime, capacity, transfer and additional features.
- Separate credits, tax and refunds; distinguish estimated from finalized charges.
Do not delete an unexpected resource immediately. Identify its owner, purpose, retained data and dependencies first. The EC2 cost lesson makes the post-stop components more concrete.
Check, then explain in your own words
- List resources and billing units.
- State assumptions and exclusions.
- Compare equivalent billing records and explain differing components.
Check your understanding: Do equal instance counts and runtime imply equal total AWS costs?
No. Storage, networking, configuration and purchase terms can differ.
OS, configuration, provisioned storage, transfer destinations, other services and credits may differ. A compute-only subtotal is not the system total.
Sources and conditions checked
The official references used in this lesson are collected here with their scope, conditions and corresponding sections. Independent expert review and live AWS comparison have not been performed.
- Understanding your billChecked:
Scope and conditionsBilling period, service/Region breakdown and estimated charges
Used in this lessonAlign units and assumptions before comparing rates Explain differences from actual charges
- Amazon EC2 pricingChecked:
Scope and conditionsRegion, OS, tenancy, instance, purchase option; no current unit rates embedded
Used in this lessonTurn the design into a cost inventory
- Understanding unexpected chargesChecked:
Scope and conditionsResources in all Regions; deletion and data retention need review
Used in this lessonExplain differences from actual charges
- Amazon EC2 On-Demand pricingChecked:
Scope and conditionsCompute assumptions, OS-specific billing granularity, data transfer and additional resource charges; no unit rates embedded.
Used in this lessonTurn the design into a cost inventory Align units and assumptions before comparing rates
- Amazon EBS pricingChecked:
Scope and conditionsProvisioned capacity, additional performance and snapshots; no unit rate or price quote is embedded.
Used in this lessonTurn the design into a cost inventory Align units and assumptions before comparing rates Worked example: separate included and unestimated costs
- Amazon VPC pricingChecked:
Scope and conditionsPublic IPv4 and NAT gateway pricing dimensions, including retained/idle addresses; no unit-rate quote.
Used in this lessonTurn the design into a cost inventory Align units and assumptions before comparing rates
- EC2 instance state changesChecked:
Scope and conditionsEBS-backed stop/start, hibernation and termination differ
Used in this lessonWorked example: separate included and unestimated costs
- Amazon S3 pricingChecked:
Scope and conditionsFee axes, binary storage GB, Region/class/count/duration conditions and replication; no live rates quoted; all classroom prices explicitly invented
Used in this lessonTurn the design into a cost inventory Align units and assumptions before comparing rates
- Amazon CloudWatch pricingChecked:
Scope and conditionsLog ingestion, storage and query dimensions depend on Region, class, feature and allowances; classroom rates are invented, not current prices.
Used in this lessonAlign units and assumptions before comparing rates
- What is AWS Pricing Calculator?Checked:
Scope and conditionsEstimates reflect entered information and exclude applicable taxes; not a final invoice or spending cap.
Used in this lessonAlign units and assumptions before comparing rates Worked example: separate included and unestimated costs