Topic lessonTopic: Account protection and resource cleanup
Stop vs terminate an EC2 instance: restartability, data retention and costs
Stop changes an instance’s state so it can later be started; terminate permanently removes the instance. Neither operation means that all data and associated charges behave identically. Use a typical EBS-backed instance to compare these actions with reboot and hibernation.
Choose between stopping and terminating for a stated purpose, and identify the data, EBS settings and retained-resource checks needed beforehand.
EBS is a storage resource separate from the instance. This lesson performs no real stop/deletion actions or commands.
Decide whether to resume it or remove the instance
- Running → StoppedNormal stop: an instance intended for later use can start again through pending/running.
- Running → TerminatedTerminate: permanently remove the instance; do not treat it as a routine pause.
- Running
- Active compute; idle time can still incur compute charges.
- Stopped
- An EBS-backed instance can be started later; retained storage costs are separate.
- Terminated
- That instance cannot be started or recovered; review data settings before the action.
| Area | Normal stop | Terminate |
|---|---|---|
| Start the same instance again | Possible | Cannot start or recover that instance |
| EBS | Retained; storage costs are separate | Each volume’s DeleteOnTermination governs its retention/deletion |
| Instance-store data | Lost | Lost |
| RAM contents | Not retained | Not retained |
| Associated resources/commitments | Inspect EBS, addresses, other components and commitments separately | Inspect retained resources and commitments separately |
Data survival depends on where the data is stored
An EBS volume differs from temporary instance store storage on the host. A normal stop retains EBS, but loses instance-store data and RAM contents. Do not assume that stopping preserves every part of an application’s working state.
For termination, inspect DeleteOnTermination per EBS volume: true selects deletion with termination; false retains the volume. Defaults depend on creation and attachment details, so “root” or “data” labels alone are not sufficient. Review charges for retained volumes separately.
Reboot and hibernation are not normal stop
| Operation | Distinction |
|---|---|
| Reboot | Restart the OS on the same host; instance-store data remains and compute charges continue |
| Normal stop | Stop EBS-backed compute without retaining RAM or instance-store data |
| Hibernate | On supported configurations, save RAM to EBS; stopping-state compute charges apply |
| Terminate | Permanently remove the instance; EBS retention/deletion settings matter |
A shutdown command inside the OS does not universally mean normal stop. For EBS-backed instances, check settings such as InstanceInitiatedShutdownBehavior. Do not infer the data or cost outcome from the command’s name alone.
Review reconnection addresses and retained charges
A stop/start retains the private IPv4 address, but a normal automatically assigned public IPv4 address can change. Check Elastic IP retention, association and release separately. Verify the actual destination instead of assuming the previous connection address still applies.
Charges for normally stopped compute are separate from EBS, snapshots, addresses, associated services and purchasing commitments. Termination does not automatically remove all of those either.
Choose an option to see the result and explanation.
A short checklist before the action
- Choose the intended outcome: later restart, OS reboot, hibernation or permanent removal.
- Locate required data in EBS, instance store or RAM.
- Review each EBS termination-deletion setting and retention/recovery requirements.
- Check addresses, service dependencies, retained resources and commitments.
- Have an authorized operator act, then verify the state and remaining resources.
Check, then explain in your own words
- Explain which operation allows the same instance to be started again.
- Separate EBS, instance-store data and RAM.
- Review termination settings, addresses and retained charges.
Check your understanding: If an EBS-backed instance is stopped, does its instance-store data survive too?
No. Instance store is separate from retained EBS.
EBS can remain while a normal stop loses instance-store data and RAM. Establish the location of required data before choosing the operation.
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.
- EC2 instance state changesChecked:
Scope and conditionsEBS-backed stop/start, hibernation and termination differ
Used in this lessonDecide whether to resume it or remove the instance Data survival depends on where the data is stored Reboot and hibernation are not normal stop Review reconnection addresses and retained charges A short checklist before the action
- Understanding unexpected chargesChecked:
Scope and conditionsResources in all Regions; deletion and data retention need review
Used in this lessonDecide whether to resume it or remove the instance Review reconnection addresses and retained charges A short checklist before the action
Scope and conditionsData loss and persistence; DeleteOnTermination is evaluated for each EBS volume, not assumed from instance state.
Used in this lessonDecide whether to resume it or remove the instance Data survival depends on where the data is stored Review reconnection addresses and retained charges A short checklist before the action
- Amazon VPC pricingChecked:
Scope and conditionsPublic IPv4 and NAT gateway pricing dimensions, including retained/idle addresses; no unit-rate quote.
Used in this lessonReview reconnection addresses and retained charges