Repository navigation
feat(aws_s3 source): support CrowdStrike FDR batch notifications in SQS - #53
Merged
Merged
Conversation
Parse CrowdStrike Falcon Data Replicator batch notifications, which list objects written to a CrowdStrike-hosted S3 bucket rather than using native S3 event notifications. The source only understood S3 event formats, so a customer who keeps the CrowdStrike-hosted feed had no way to ingest it. Convert each listed file into a standard S3 object-created event and pass it through the existing S3 event processing path. Use the queue's AWS region and the notification timestamp, allowing FDR objects to reuse the existing S3 ingestion logic without a separate processing path.
pupapaik
approved these changes
Nov 13, 2026
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.
Parse CrowdStrike Falcon Data Replicator batch notifications, which list objects written to a CrowdStrike-hosted S3 bucket rather than using native S3 event notifications. The source only understood S3 event formats, so a customer who keeps the CrowdStrike-hosted feed had no way to ingest it.
Convert each listed file into a standard S3 object-created event and pass it through the existing S3 event processing path. Use the queue's AWS region and the notification timestamp, allowing FDR objects to reuse the existing S3 ingestion logic without a separate processing path.