I'm trying to write a cross account aws cli command to subscribe to a topic and create a filter for that subscription at the same time. Below is how my command looks like.
aws sns subscribe --topic-arn arn:aws:sns:region:accountId:my_topic --protocol sqs --notification-endpoint arn:aws:sqs:region:differentAccountId:my_sqs_queue --attributes "{'RawMessageDelivery': 'true', 'FilterPolicy': '{\"filter\": [\"value1\", \"value2\"]}'}"
I'm getting below error when I run this.
Unknown options: --attributes, [\value1\,, \value2\]}'}, {'RawMessageDelivery': 'true', 'FilterPolicy': '{" filter\:
I've access to admin access both the aws accounts. Any suggestions on what I'm doing wrong?
EDIT: I'm running this in VS Code powershell terminal in windows.
There's probably an easier way to do it (eg using --cli-input-json and providing JSON in a file), but I got this working:
aws sns subscribe \
--topic-arn arn:aws:sns:region:accountId:my_topic \
--protocol sqs \
--notification-endpoint arn:aws:sqs:region:differentAccountId:my_sqs_queue \
--attributes '{\"RawMessageDelivery\": \"true\", \"FilterPolicy\": \"{\\\"filter\\\": [\\\"value1\\\", \\\"value2\\\"]}\"}'
The problem was the JSON included in a string, which needed \" to be escaped as \\\".
This Github repo has an example: https://github.com/Haple/sns-sqs-subscribe
#!/bin/sh
# SETUP
queue_arn=$(awslocal sqs create-queue --queue-name test_queue --output text)
echo "Queue ARN: $queue_arn"
topic_arn=$(awslocal sns create-topic --name test_topic --output text)
echo "Topic ARN: $topic_arn"
subscription_arn=$(awslocal sns subscribe \
--topic-arn "$topic_arn" \
--protocol sqs \
--notification-endpoint "$queue_arn" \
--output text)
echo "Subscription ARN: $subscription_arn"
awslocal sns set-subscription-attributes \
--subscription-arn "$subscription_arn" \
--attribute-name FilterPolicy \
--attribute-value "{ \"EVENT_TYPE\": [\"SUCCESS\"] }"
# TEST
awslocal sns publish \
--topic-arn "$topic_arn" \
--message "SUCCESS PAYLOAD (SHOULD GO TO THE QUEUE)" \
--message-attributes '{"EVENT_TYPE" : { "DataType":"String", "StringValue":"SUCCESS"}}'
awslocal sns publish \
--topic-arn "$topic_arn" \
--message "ERROR PAYLOAD (SHOULD NOT GO TO THE QUEUE)" \
--message-attributes '{"EVENT_TYPE" : { "DataType":"String", "StringValue":"ERROR"}}'
awslocal sqs get-queue-attributes \
--queue-url http://localhost:4576/queue/test_queue \
--attribute-names AllThe overall process in the previous answers is OK, but there is a huge issue:
I do not know why no one is mentioning this, but the whole thing doesn't work if you do not set the SQS queue policy document correctly.
The github example doesn't do it and for some reason, AWS documentation doesn't even mention it.
Refer to this question: Set SQS policy document with AWS CLI
I wasted a couple of days troubleshooting this. So hope it helps.