Hands-on emulator lab · 6–10 min
Handle a rush without hammering your API — API Gateway and Throttling
Set and inspect a burst limit on an HTTP API stage.
These actions use an isolated AWS Emulator. It stores API state locally; it does not create paid cloud resources or run the full hosted AWS service.
Your goal
Set and inspect a burst limit on an HTTP API stage.
Why this matters
An API stage can limit the rate and short bursts it aims to accept. You will choose a burst allowance and inspect the stage setting. This lab does not load-test enforcement.
Words you will use
A rate is requests over time. A burst is a short rush. Throttling rejects some requests when targets are exceeded. Backoff means waiting longer between retries.
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 an API stage
Create an HTTP API and a practice stage with automatic deployment enabled. A stage is a named version of an API configuration. No public traffic is generated by this lab.
2. Set a small burst allowance
Choose the short-burst allowance and save a steady rate of five requests per second. Throttling settings help control demand; they are not a guarantee that every excess request is blocked.
Burst allowance: Choose 5–50 requests for this practice setting. Suggested practice value: 10.
3. Inspect the saved stage
Get the stage and inspect its default route settings. The lab checks your burst value. It does not load-test an endpoint or measure rejected requests.
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.