Give each subscriber the messages it needs — SNS and Subscription filters

Your goal

Give an SNS subscription a filter for one kind of message.

Why this matters

Different subscribers may want different kinds of update. You will save a kind filter on one subscription and inspect its scope. This lab checks the filter configuration, not message delivery.

Words you will use

A topic publishes messages. A subscription connects a recipient. A filter policy selects messages using attributes or a JSON message body.

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 subscription

Create a topic, a queue, and the subscription joining them. The queue is one subscriber’s inbox. Each subscriber can have its own filter.

2. Choose the message kind

Save a filter policy on message attributes. Choose order or upload as the kind this subscriber wants. A publisher must send the matching attribute for this filter to apply.

Message kind: This filters the kind message attribute, not arbitrary words in the body. Suggested practice value: order.

3. Inspect the filter policy

Read the subscription attributes and find your chosen kind in FilterPolicy. This exercise verifies the saved filter, not delivery or rejection of a published message.

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.