What is the difference between attribute-based and payload-based filtering?

Attribute-based filtering (the default) matches against message attributes — key-value pairs set when publishing. Payload-based filtering matches against fields in the message body (JSON). Attribute-based filtering is more efficient because SNS evaluates attributes without parsing the message body. Payload-based filtering is useful when publishers cannot add message attributes or when the filtering criteria exist only in the message payload. You set the filter policy scope to MessageAttributes or MessageBody when creating the subscription.

How do filter policy operators work?

Filter policies support several operators: exact string match (plain string values), prefix match ({"prefix": "value"}), numeric comparisons ({"numeric": [">", 100]}), anything-but ({"anything-but": ["value"]}), exists ({"exists": true}), and combinations. Within a single attribute, multiple values use OR logic — the message matches if any value matches. Across different attributes, AND logic applies — all attributes must match. This lets you build complex routing rules like 'event_type is order AND priority is greater than 5'.

SNS Filter Policy Builder

ServerlessAWS

Build SNS subscription filter policies with attribute matching and operators.

SNS Filter Policy Configuration

Filter Scope

Attribute 1

Attribute Name

Match Type

Values (comma-separated)

Generated SNS Filter Policy

Output will appear here...

About This Tool

SNS subscription filter policies let subscribers receive only the messages they care about, reducing unnecessary processing and cost. A filter policy is a JSON document that defines attribute-matching rules using exact values, prefix matching, numeric comparisons, existence checks, and logical operators. With SNS supporting both message-attribute filtering and message-body filtering (payload-based), choosing the right approach and constructing correct filter syntax is essential. The SNS Filter Policy Builder generates valid filter policy JSON with the correct operator syntax for common filtering patterns.

When to Use This Tool

•Building filter policies that route order events to different SQS queues based on order type and priority attributes
•Creating numeric range filters that send only high-value transaction notifications to a processing Lambda
•Defining prefix-based filters that route events by region or service namespace to the appropriate subscribers
•Constructing compound filter policies with AND/OR logic across multiple message attributes

Frequently Asked Questions

What is the difference between attribute-based and payload-based filtering?: Attribute-based filtering (the default) matches against message attributes — key-value pairs set when publishing. Payload-based filtering matches against fields in the message body (JSON). Attribute-based filtering is more efficient because SNS evaluates attributes without parsing the message body. Payload-based filtering is useful when publishers cannot add message attributes or when the filtering criteria exist only in the message payload. You set the filter policy scope to MessageAttributes or MessageBody when creating the subscription.
How do filter policy operators work?: Filter policies support several operators: exact string match (plain string values), prefix match ({"prefix": "value"}), numeric comparisons ({"numeric": [">", 100]}), anything-but ({"anything-but": ["value"]}), exists ({"exists": true}), and combinations. Within a single attribute, multiple values use OR logic — the message matches if any value matches. Across different attributes, AND logic applies — all attributes must match. This lets you build complex routing rules like 'event_type is order AND priority is greater than 5'.

Related Learning Guides

SQS vs SNS vs EventBridge25 min read

Disclaimer: This tool runs entirely in your browser. No data is sent to our servers. Always verify outputs before using them in production. AWS, Azure, and GCP are trademarks of their respective owners.