Request and cancel Spot capacity — EC2 and Spot

Your goal

Request Spot capacity, cancel the request, and inspect its state.

Why this matters

Interruptible capacity uses a request lifecycle that differs from keeping a server forever. You will create and cancel a Spot request, then inspect its state. Cancelling a request is separate from stopping an already-running instance.

Words you will use

Spot uses spare compute capacity that can be reclaimed. A Spot request asks for that capacity. An image record describes a machine template. Cancelling a request changes the request, not necessarily an instance that already exists.

How to proceed

Start a fresh emulator, read each numbered step, and enter the practice settings shown. Run the action, inspect its API receipt, then continue. Finish lab checks the emulator state again before saving your progress.

1. Create a Spot request

Request one small instance using a one-time Spot request. Spot capacity can be interrupted. This creates a local emulator request and does not start a real operating system or incur a charge.

2. Cancel the capacity request

Cancel the request using its returned ID. On AWS, cancelling a request and terminating an already-running instance are separate actions. This exercise changes the request record only.

3. Inspect the request state

Describe the same request and find its cancelled state. This verifies the request lifecycle. It does not measure price, reserve capacity, or simulate an interruption warning.

Practice, then check your understanding

Perform the actions yourself and inspect the returned state. Errors keep your settings so you can retry. Starting another lab clears the previous live environment. Earned XP is kept, and signed-in achievements sync to your account. Replay does not award duplicate XP.

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