Executable emulator lab · 3–5 min
EC2 stop and restart
Launch a server, predict what survives stopping, then stop and restart the same instance. Its identity is the clue.
This lab uses your own temporary emulator. It does not access a live AWS account.
Choose this lab in Missions1. Launch a server
Deploy the EC2 block. Observe the actual emulator state changing from pending to running. The block represents an EC2 instance lifecycle; it is not a virtual machine you can log into or use to run arbitrary software.
2. Predict what survives
Before stopping, inspect the resource identity. Stopping and terminating are different operations. A stopped instance retains its identity and can be started again; termination removes the instance from use.
3. Stop and restart
Stop the instance and wait for stopped. The lights become gray and still. Start the same instance again, wait for running, and compare the instance ID. The lesson validates the stopped state and subsequent restart.
4. Know the boundary
This emulator lesson teaches state and identity, not real EC2 billing or every storage behavior. On real AWS, data persistence depends on the storage involved and other configuration. Read the EC2 documentation before treating this simplified model as a production operating procedure.
Practice, then check your understanding
Repeat the lab with different input. Explain the result before claiming completion. Your live resources expire after inactivity, while graph intent and earned XP remain in your browser.
Read the official AWS documentation for service behavior and production details.