Run a job at the right time — EventBridge Scheduler

Your goal

Save a recurring queue schedule without turning on automatic delivery.

Why this matters

Recurring work needs a schedule, a destination, and a role. You will configure those pieces and keep the schedule disabled for practice. No background job is claimed to have run.

Words you will use

A schedule defines when work starts. A time zone gives local time meaning. An execution role grants the scheduler permission to call its target. A retry is another attempt.

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. Prepare a schedule group and destination

Create a schedule group, an SQS queue, and a scheduler role. A group organizes schedules. The queue is where scheduled work would be sent.

2. Choose a repeat interval

Create a schedule with your chosen interval and a fixed practice payload. Keep it DISABLED while learning. Saving a disabled schedule prevents this exercise from leaving recurring work running.

Minutes between scheduled jobs: Choose 2–60 minutes. This practice schedule stays disabled. Suggested practice value: 5.

3. Read the schedule expression

Retrieve the schedule and inspect its rate, target, and disabled state. This lab checks saved scheduling configuration; it does not wait for or claim an automatic invocation.

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.