-
Notifications
You must be signed in to change notification settings - Fork 444
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
[Jamf Protect] Adding AWS S3 as input type #9643
Conversation
/test |
🚀 Benchmarks reportPackage
|
Data stream | Previous EPS | New EPS | Diff (%) | Result |
---|---|---|---|---|
alerts |
1501.5 | 1077.59 | -423.91 (-28.23%) | 💔 |
To see the full report comment with /test benchmark fullreport
💚 Build Succeeded
|
Quality Gate passedIssues Measures |
Pinging @elastic/security-service-integrations (Team:Security-Service Integrations) |
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
Package jamf_protect - 0.4.0 containing this change is available at https://epr.elastic.co/search?package=jamf_protect |
Bug
Added AWS-S3 Input to each data stream
Jamf Protect supports forwarding event data to AWS S3, this provides an alternative route alongside HTTP Endpoint
Checklist
changelog.yml
file.How to test this PR locally
Screenshots