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

EC2 costs explained: instances, EBS, IPs, transfer and retained charges

Separate instance compute charges from associated resources. A normal stop can end instance usage charges while EBS, snapshots or retained IP resources remain. Review purchase commitments and the network design alongside the instance.

What you will learn

Identify EC2 pricing assumptions and associated resources, and explain what remains to review after stopping.

Prerequisite

Know EC2, EBS and Regions. This lesson neither calculates a bill nor changes real resources.

“One EC2 instance” does not define a price

Compute pricing assumptions
AssumptionCheck
Region and configurationLocation, instance type, OS, tenancy and count
Time and unitsRuntime and applicable minimum/granularity for the OS and offer
Purchase optionOn-Demand, Spot, Savings Plans and their conditions/obligations
Additional dimensionsAMI software charges and applicable performance/CPU-credit dimensions

Do not assume identical per-second billing for every OS. Check the offer’s OS coverage, granularity and minimum. Options with usage commitments do not lose their contractual obligations merely because the current instance stops.

Associated resources have their own lifetimes

EC2 and separately reviewed cost components
EC2 and separately reviewed cost components1: EC2 instance — A normal stop does not release EBS. — EBS / snapshots. 2: EC2 instance — Instance state alone does not determine every IP/network-service charge. — IPs / networking. 3: EC2 instance — Distinguish resource usage from contractual payment obligations. — Purchase terms123EC2 instanceEBS / snapshotsIPs / networkingPurchase termsEC2 and separately reviewed cost components1: EC2 instance — A normal stop does not release EBS. — EBS / snapshots. 2: EC2 instance — Instance state alone does not determine every IP/network-service charge. — IPs / networking. 3: EC2 instance — Distinguish resource usage from contractual payment obligations. — Purchase terms123EC2 instanceEBS / snapshotsIPs /networkingPurchase terms
  1. EC2 instance → EBS / snapshotsA normal stop does not release EBS.
  2. EC2 instance → IPs / networkingInstance state alone does not determine every IP/network-service charge.
  3. EC2 instance → Purchase termsDistinguish resource usage from contractual payment obligations.
EC2 instance
Review compute state and applicable usage charges.
EBS / snapshots
Storage, performance and retention have separate dimensions.
IPs / networking
Review retained addresses, NAT and transfer.
Purchase terms
Review commitments that can outlast an instance.
After a normal stop
ComponentReason to review
EBS volumesProvisioned capacity/performance, even if few files are stored
SnapshotsStored data and added features, separate from the source instance
Elastic IPs and other addressesDetachment and release differ; retained idle addresses need review
Services such as NATIndependent service-hours and processing dimensions
Reservations / Savings PlansReview contractual duration and payment terms separately

Stop, hibernate and terminate are different

Compute-state distinctions
OperationCharges and data to inspect
Normal stopDistinguish compute usage in stopping/stopped from retained EBS and other resources
HibernateThe stopping phase is billed; review EBS holding RAM data too
TerminateThe instance cannot restart; inspect each EBS DeleteOnTermination setting, retained resources and contracts

Choose an option to see the result and explanation.

An Elastic IP remains unassociated after stopping. Is it safe to ignore because it is unused?
Read the answer and reason

Answer: No; review its pricing and purpose · Disassociation is different from release. Review retained-address pricing and any reuse or dependency requirements with the owner.

Estimate through the end of the exercise

  1. Record Region, instance configuration, OS, count, runtime and purchase option.
  2. Add EBS capacity/performance and retained snapshots.
  3. Add IPs, transfer source/destination and services such as NAT.
  4. Review resource-retention periods and commitments, not just stop time.
  5. Estimate with official terms, then compare equivalent billing periods.

Check, then explain in your own words

  1. Separate compute assumptions from storage and networking.
  2. Explain stop, hibernate and terminate.
  3. Reconcile retained resources and commitments with billing.
Check your understanding: Does terminating an instance remove every related charge?

No. Retained resources and contracts need separate review.

EBS, snapshots, addresses, surrounding services or commitments may persist. Resource state and the billing period also need separate inspection.

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.