-
Notifications
You must be signed in to change notification settings - Fork 522
[aws] Add S3 option to s3access logs #10460
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
Conversation
🚀 Benchmarks reportPackage
|
| Data stream | Previous EPS | New EPS | Diff (%) | Result |
|---|---|---|---|---|
inspector |
1805.05 | 1438.85 | -366.2 (-20.29%) | 💔 |
securityhub_findings |
1102.54 | 900.09 | -202.45 (-18.36%) | 💔 |
waf |
6849.32 | 5263.16 | -1586.16 (-23.16%) | 💔 |
apigateway_logs |
11363.64 | 4065.04 | -7298.6 (-64.23%) | 💔 |
cloudwatch_logs |
500000 | 250000 | -250000 (-50%) | 💔 |
To see the full report comment with /test benchmark fullreport
zmoog
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
MichaelKatsoulis
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
agithomas
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
💚 Build Succeeded
History
|
|
|
Package aws - 2.20.0 containing this change is available at https://epr.elastic.co/search?package=aws |




Proposed commit message
This PR is to add reading logs directly from S3 as an option for
s3accessdata stream. There are more data streams need this change, will add it later in the same PR.Checklist
changelog.ymlfile.Screenshots
I tested it with a sample log file just with content

test1. It's not an s3acecss log so it shows it cant be parsed. But the message got ingested from s3 to elastic:The agent policy looks like this: