Fan out SNS messages to multiple SQS queues with subscription filter policies

Steps

1. Create an SNS topic (Standard for fan-out, FIFO only if strict ordering is required across all subscribers); create one SQS queue per downstream consumer
2. Subscribe each SQS queue to the SNS topic; grant SNS permission to send to each SQS queue by attaching a queue policy that allows sns:SendMessage from the topic ARN
3. Set a subscription filter policy (JSON object matching message attributes) on each subscription so each queue only receives relevant message subsets — this reduces processing cost and simplifies consumer logic
4. When publishing, include MessageAttributes that match your filter policy keys and values; messages without the required attributes are filtered out at the SNS level (not delivered to that subscription)
5. Enable raw message delivery on the SQS subscription if you want SQS consumers to receive the original message body without the SNS JSON envelope; leave it disabled if consumers need SNS metadata like TopicArn or MessageId
6. For cross-account fan-out, add the receiving account's SQS queue ARN to the subscription and ensure both the queue policy and the SNS topic policy allow the cross-account action