This repository has been archived by the owner on Jun 8, 2023. It is now read-only.
SRE-7111 - Add a second handler to handle SNS events #26
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The S3Event is wrapped with an SNS event wrapper object when it is delivered to the lambda to pushes events to elastic search. The entire configuration and the code is almost the same as the handler for S3Event, except that the ElastisLambdaSNSForwarder unpacks the received SNSEvent to extract the S3Event.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The S3Event is wrapped with an SNS event wrapper object when it is
delivered to the lambda to pushes events to elastic search. The entire
configuration and the code is almost the same as the handler for
S3Event, except that the ElastisLambdaSNSForwarder unpacks the received
SNSEvent to extract the S3Event.