INFRASTRUCTURE LEARNINGINFRASTRUCTURE LEARNING
インフラ大全インフラ大全IT INFRASTRUCTURE / LEARNING
Infrastructure learning guide
Find a lesson or lab/

Esc to close · Search terms stay on your device

LEARNING日本語

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.

What you will learn

List a small design’s cost dimensions and assumptions, and distinguish an estimate from metered usage and billing.

Prerequisite

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

Representative compute, storage and network costs; include requests and logs from the next table
Representative compute, storage and network costs; include requests and logs from the next table1: Compute — Include compute dimensions. — Estimate scope. 2: Storage — Account separately for storage. — Estimate scope. 3: Network services — Include network and surrounding services; the lines do not describe packet flow. — Estimate scope123ComputeStorageNetwork servicesEstimate scopeRepresentative compute, storage and network costs; include requests and logs from the next table1: Compute — Include compute dimensions. — Estimate scope. 2: Storage — Account separately for storage. — Estimate scope. 3: Network services — Include network and surrounding services; the lines do not describe packet flow. — Estimate scope123ComputeStorageNetworkservicesEstimate scope
  1. Compute → Estimate scopeInclude compute dimensions.
  2. Storage → Estimate scopeAccount separately for storage.
  3. 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

Five cost dimensions and comparison conditions to check for the services you use
DimensionQuantity or conditionExample omission
ComputeRegion, instance type, OS, count, runtime, purchase option and billing unitTreating the server hourly rate as the price of the whole system
StorageProvisioned EBS capacity/performance, S3 class/amount/duration and snapshotsAssuming stopped compute means storage charges have ended
Transfer and processingSource, destination, direction, AZ/Region and NAT time/processingAssuming a transfer price includes every NAT processing charge
RequestsGET, PUT or other request types and counts in the pricing table’s unitsCounting stored data but omitting read/write requests
LogsIngested amount, stored amount/duration and queried data under feature-specific termsAssuming ingestion includes all storage and querying
Comparison conditionsEquivalent period, scope and currency; tax, discounts, credits and allowancesReplacing 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

Five items calculated with invented rates; add the costs, not the different quantities
Included itemStipulated quantityInvented rateCost
Compute1 instance × 10 hours = 10 instance-hours$0.10 / instance-hour$1.00
Selected S3 storage2 GB-month$0.05 / GB-month$0.10
Covered transfer3 GB$0.20 / GB$0.60
Selected S3 GET requests2,000 = 2 × 1,000 requests$0.03 / 1,000 requests$0.06
Log ingestion only1 GB$0.50 / GB$0.50
Selected five-row subtotalSum money, not incompatible quantities—$2.26

Choose an option to see the result and explanation.

What is the subtotal for only the five listed rows?
Read the answer and reason

Answer: $2.26 · 1.00 + 0.10 + 0.60 + 0.06 + 0.50 = 2.26 for the selected rows. It is not the amount for a complete design with unestimated components.

The $2.26 includes log ingestion, but stored/query volumes are unknown. What does the amount represent?
Read the answer and reason

Answer: A selected subtotal; establish and add applicable missing items · Unknown quantities are not evidence of zero cost. Check ingestion, storage, querying and other items. This subtotal does not establish a final bill or a cap; unresolved charges and adjustments can change the final amount in either direction.

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.

EC2 stops after an hour, but EBS is retained. Is one hour of compute the entire cost?
Read the answer and reason

Answer: No; review storage separately · Stopping compute does not release retained EBS. Review provisioned storage and its retention period separately.

Explain differences from actual charges

  1. Align period, account scope, currency and cost metric.
  2. Find service/Region lines that differ from the estimate.
  3. Investigate count, runtime, capacity, transfer and additional features.
  4. 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

  1. List resources and billing units.
  2. State assumptions and exclusions.
  3. 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.

This exercise is currently unavailable. The article and existing lessons remain available.