You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I find that this plugin works well for 1:1 message transfer between sns and sqs, but do you support sqs with multiple subscriptions. My use case requires the use of the SNS fanout pattern, so I'm wondering what the configuration would look like. I tried the most obvious config below, but I only see one (the last) subscription bound to my SQS queue.
I think this isn't working because the CloudFormation logical IDs are generated based on the name attribute, so your two snsSqs definitions are conflicting with each other. In fact, I think after #552 lands, you would get an error instead of a silent failure. It seems somewhat related to #444
I'll do some testing at some point,. In the meantime, you might be able to get it to work by giving each event definition a different name attribute. For example:
I find that this plugin works well for 1:1 message transfer between sns and sqs, but do you support sqs with multiple subscriptions. My use case requires the use of the SNS fanout pattern, so I'm wondering what the configuration would look like. I tried the most obvious config below, but I only see one (the last) subscription bound to my SQS queue.
In serverless.yml I could do something like this, but I want to use your integration to have a queue between them:
Appreciate any suggestions.
The text was updated successfully, but these errors were encountered: