Give a function enough time, with a limit — Lambda and Timeouts

Your goal

Change a function’s time limit and read the saved limit back.

Why this matters

A function needs enough time to finish, but an endless wait is not useful. You will choose a timeout and verify its stored value. This exercise configures the limit; it does not benchmark a workload.

Words you will use

A timeout stops a run after its time limit. A retry is another attempt. A time budget divides the available time between calls and cleanup.

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 your practice function

Create a Lambda function using the site’s fixed practice handler. Wait for its state to become Active. Your function has its own name and role in this emulator.

2. Set the time budget

Enter a timeout for the practice function. A bounded run needs enough time for its work, while network calls should leave room for error handling. Save your chosen value.

Function timeout in seconds: Choose 1–60 seconds for this short practice function. Suggested practice value: 10.

3. Read the function setting

Retrieve the setting from the emulator and compare it with your input. The returned state is the evidence used to complete this lab.

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.