EC2 stop and restart

Your goal

Show that stopping a server is different from removing it.

Why this matters

You may need to pause a server without throwing it away. You will watch its state change and compare its ID before and after a restart. This lab models the server lifecycle; it does not start a computer you can log into.

Words you will use

An EC2 instance is a cloud server. Running means it is on. Stopped means it is paused. Terminated means it has been removed from use. An instance ID identifies one server.

How to proceed

Open the lab, read the goal, then follow the numbered steps. Each step names the controls and explains the result to look for.

1. Launch your server

Click Start building or Deploy stack to create the EC2 instance. Wait for the block to say running. Select it to see its instance ID, the label that identifies this server. Keep that ID in mind for the last step.

2. Predict what stopping changes

Click Next step to open the question. Decide whether Stop removes the server or pauses it so the same one can run again. This question is about its identity, not every kind of disk data.

3. Stop and inspect the server

Select the EC2 block and click Stop instance. Wait until the state says stopped and its lights go dark. Look at the instance ID. Do not remove the block: stopping and removing are different actions.

4. Start the same server again

In the same block’s controls, click Start instance. Wait until the state says running. Compare the instance ID with the one you saw earlier. It should be the same. You have now shown that a stopped instance can restart; finish the mission to record it.

Practice, then check your understanding

Repeat the lab with different input. Explain the result before claiming completion. Your live resources expire after inactivity, while your canvas stays in this browser. Guest XP stays here too; signed-in achievements sync to your account.

Read the official AWS documentation for service behavior and production details.