Hands-on emulator lab · 6–10 min
Connect a queue to a workflow — EventBridge Pipes and SQS and Step Functions
Configure a stopped pipe between a source queue and a destination queue.
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
Configure a stopped pipe between a source queue and a destination queue.
Why this matters
A pipe defines a connection between an event source and a destination. You will connect two queue records and keep the pipe stopped. The stored connection can be inspected before requesting processing.
Words you will use
A pipe connects one supported source to one target. Filtering selects events. Transformation changes the event shape before delivery.
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 both ends and a role
Create a source queue, a target queue, and a role for EventBridge Pipes. A pipe connects an event source to a destination with optional filtering and transformation.
2. Save the pipe configuration
Create the pipe using the two queue ARNs and the role. Keep its desired state STOPPED. This lets you inspect the connection before any background processing is requested.
3. Check both endpoints and state
Describe the pipe and compare source, target, and desired state with your setup. This lab checks configuration, not automatic message movement or permission enforcement.
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.