Rin does not support messages from s3->sns->sqs, only messages from s3->sqs

[superosku]

We had this issue where we wan't two process to listen for s3 events. Aws does not allow two sqs queues to listen to the same kind of events on the same bucket. The correct way around this is to put s3 events into sns queue that can then be listened by multiple destinations.

There is an issue with this approach and rin. Sns wraps the events into another layer of json document that needs to be unmarshalled.

[fujiwara]

Thank you! v1.2.0 released. https://github.com/fujiwara/Rin/releases/tag/v1.2.0