Splunk HEC support #72
Open
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR will provide the ability to push Antiope Resources to Splunk via the HEC (rather than via scanning the S3 bucket). It includes changes to the S3 Bucket, the ElasticSearch stack, and a new Template to deploy the Stack that does the HEC Push.
The ElasticSearch changes are necessary because the Antiope Bucket now sends new event notifications to SNS (rather than directly to SQS), so the format and structure of the event the ElasticSearch ingest function needs to process has changed somewhat. These changes should be backwards compatible, but testing is recommended.