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.
Identify EC2 pricing assumptions and associated resources, and explain what remains to review after stopping.
Know EC2, EBS and Regions. This lesson neither calculates a bill nor changes real resources.
“One EC2 instance” does not define a price
| Assumption | Check |
|---|---|
| Region and configuration | Location, instance type, OS, tenancy and count |
| Time and units | Runtime and applicable minimum/granularity for the OS and offer |
| Purchase option | On-Demand, Spot, Savings Plans and their conditions/obligations |
| Additional dimensions | AMI 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 instance → EBS / snapshotsA normal stop does not release EBS.
- EC2 instance → IPs / networkingInstance state alone does not determine every IP/network-service charge.
- 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.
| Component | Reason to review |
|---|---|
| EBS volumes | Provisioned capacity/performance, even if few files are stored |
| Snapshots | Stored data and added features, separate from the source instance |
| Elastic IPs and other addresses | Detachment and release differ; retained idle addresses need review |
| Services such as NAT | Independent service-hours and processing dimensions |
| Reservations / Savings Plans | Review contractual duration and payment terms separately |
Stop, hibernate and terminate are different
| Operation | Charges and data to inspect |
|---|---|
| Normal stop | Distinguish compute usage in stopping/stopped from retained EBS and other resources |
| Hibernate | The stopping phase is billed; review EBS holding RAM data too |
| Terminate | The instance cannot restart; inspect each EBS DeleteOnTermination setting, retained resources and contracts |
Choose an option to see the result and explanation.
Estimate through the end of the exercise
- Record Region, instance configuration, OS, count, runtime and purchase option.
- Add EBS capacity/performance and retained snapshots.
- Add IPs, transfer source/destination and services such as NAT.
- Review resource-retention periods and commitments, not just stop time.
- Estimate with official terms, then compare equivalent billing periods.
Check, then explain in your own words
- Separate compute assumptions from storage and networking.
- Explain stop, hibernate and terminate.
- 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.
- Amazon EC2 pricingChecked:
Scope and conditionsRegion, OS, tenancy, instance, purchase option; no current unit rates embedded
Used in this lesson“One EC2 instance” does not define a price
- EC2 instance state changesChecked:
Scope and conditionsEBS-backed stop/start, hibernation and termination differ
Used in this lessonAssociated resources have their own lifetimes Stop, hibernate and terminate are different
- Understanding unexpected chargesChecked:
Scope and conditionsResources in all Regions; deletion and data retention need review
Used in this lesson“One EC2 instance” does not define a price Associated resources have their own lifetimes Estimate through the end of the exercise
- 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 lesson“One EC2 instance” does not define a price Estimate through the end of the exercise
- Amazon EBS pricingChecked:
Scope and conditionsProvisioned capacity, additional performance and snapshots; no unit rate or price quote is embedded.
Used in this lessonAssociated resources have their own lifetimes Estimate through the end of the exercise
- Amazon VPC pricingChecked:
Scope and conditionsPublic IPv4 and NAT gateway pricing dimensions, including retained/idle addresses; no unit-rate quote.
Used in this lessonAssociated resources have their own lifetimes Stop, hibernate and terminate are different Estimate through the end of the exercise
Scope and conditionsData loss and persistence; DeleteOnTermination is evaluated for each EBS volume, not assumed from instance state.
Used in this lessonStop, hibernate and terminate are different