-
-
Notifications
You must be signed in to change notification settings - Fork 256
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AWS SNS support would be great #40
Comments
Hey! Thanks for pointing out. As per documentation AWS SNS is not a protocol but a product supporting many protocols:
http://docs.aws.amazon.com/sns/latest/api/API_Subscribe.html So in which protocol would you be interested? |
I'm closing the issue as it's already a week old without response. Feel free keep commenting. |
Somehow my notification for this went missing. So while SNS does support multiple methods to subscribe to it, that I see is some 'implementation' logic. At the very least, the ability to specify that the API is SNS. Perhaps have the ability so specify the account id, region etc would be great. This could perhaps be used to build up the ARN? With regards to consuming a message, I believe the event data will be the same regardless of which approach you use to subscribe to it. I have also tried the approach of setting the base topic to represent the ARN, but when it joins the actual stream, it uses a |
I think your best friend here is Specification Extensions. x-sns-region: 'us-east-1'
x-sns-accountId: 'your-account-id-here' The only thing you'd have to do is to tweak documentation generator and/or code generator to use those values. |
Currently covering our topics with this and it would be great to have some official SNS support
edit: incorrectly used
sqs
instead ofsns
The text was updated successfully, but these errors were encountered: