-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
[Filebeat] Add fileset for AWS CloudTrail #14657
Labels
Comments
Pinging @elastic/siem (Team:SIEM) |
PR: #15227 |
leehinman
added a commit
to leehinman/beats
that referenced
this issue
Jan 13, 2020
- maps all fields in CloudTrail events - requestParameters, responseElements, additionalEventData & serviceEventDetails are string representations - add event.original - add event.type - add event.kind - add event.outcome - run geoip processor - run agent processor - populated related.user array when possible - uses s3input - CloudTrail must write to S3 bucket, and send all Create Events to an SQS queue we listen to Fixes elastic#14657
leehinman
added a commit
to leehinman/beats
that referenced
this issue
Jan 13, 2020
- maps all fields in CloudTrail events - requestParameters, responseElements, additionalEventData & serviceEventDetails are string representations - add event.original - add event.type - add event.kind - add event.outcome - run geoip processor - run agent processor - populated related.user array when possible - uses s3input - CloudTrail must write to S3 bucket, and send all Create Events to an SQS queue we listen to Fixes elastic#14657 (cherry picked from commit da7a697)
leehinman
added a commit
that referenced
this issue
Jan 14, 2020
- maps all fields in CloudTrail events - requestParameters, responseElements, additionalEventData & serviceEventDetails are string representations - add event.original - add event.type - add event.kind - add event.outcome - run geoip processor - run agent processor - populated related.user array when possible - uses s3input - CloudTrail must write to S3 bucket, and send all Create Events to an SQS queue we listen to Fixes #14657 (cherry picked from commit da7a697)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add a fileset to the existing aws module in Filebeat that ingests CloudTrail logs that are stored in S3. The fileset can make use of the s3 input that receives SQS notifications when a new log file is available in S3.
The text was updated successfully, but these errors were encountered: