agiledigital / agiledigital/serverless-sns-sqs-lambda

Support for fanout pattern (multiple subscriptions)

Aperta
#521 1 commento 0 reazioni 0 assegnatari Vedi su GitHub
Lingua principale
TypeScript
Stelle
85
Fork
20
Metriche di merge delle PR
Nessuna PR unita negli ultimi 30g

Descrizione

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.

```
functions:
processEvent:
handler: handler.backofficeConsumer
events:
- snsSqs:
name: sqsbackoffice
topicArn: !Ref RegisterBroker
- snsSqs:
name: sqsbackoffice
topicArn: !Ref UpdateBroker

resources:
Resources:
RegisterBroker:
Type: AWS::SNS::Topic
Properties:
TopicName: sns-register-broker
UpdateBroker:
Type: AWS::SNS::Topic
Properties:
TopicName: sns-update-broker
```

In serverless.yml I could do something like this, but I want to use your integration to have a queue between them:

```
functions:
hello:
handler: handler.run
events:
- sns:
arn: arn:aws:sns:us-east-1:00000000000:topicname
topicName: topicname-account-1-us-east-1
- sns:
arn: arn:aws:sns:us-east-1:11111111111:topicname
topicName: topicname-account-2-us-east-1
```

Appreciate any suggestions.

Guida per i contributori

Nessuna guida per i contributori indicizzata per questo repository

Valutazione

Questa issue non è ancora stata valutata.

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.