Send one update to two teams — SNS and SQS

Your goal

Publish one update and retrieve a copy from each of two subscribed queues.

Why this matters

One update may need to reach two independent teams. You will publish once and retrieve a copy from each subscribed queue. Each team gets its own message to process.

Words you will use

A topic is an announcement channel. A subscription chooses where announcements go. Fan-out means sending a copy to each listener.

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 topic and two inboxes

Create an SNS topic and two SQS queues. The topic is the announcement channel; each queue is a separate subscriber’s inbox. These are local emulator resources.

2. Subscribe both inboxes and publish

Allow the topic to send to each queue, subscribe both queues, and publish your message. One publish request should give both subscribers their own copy.

Practice message: Type a short message that you can recognize in the API result. Suggested practice value: Hello from my lab.

3. Read both copies

Receive a message from each queue and compare its contents with your update. The lab leaves messages visible so its final verification can read them again. This checks actual emulated fan-out delivery.

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.