[AWS] update max_number_of_messages parameter description#10480
[AWS] update max_number_of_messages parameter description#10480kaiyan-sheng merged 7 commits intoelastic:mainfrom
Conversation
🚀 Benchmarks reportPackage
|
| Data stream | Previous EPS | New EPS | Diff (%) | Result |
|---|---|---|---|---|
s3access |
5376.34 | 3802.28 | -1574.06 (-29.28%) | 💔 |
vpcflow |
8000 | 6369.43 | -1630.57 (-20.38%) | 💔 |
ec2_logs |
41666.67 | 32258.06 | -9408.61 (-22.58%) | 💔 |
emr_logs |
31250 | 12345.68 | -18904.32 (-60.49%) | 💔 |
To see the full report comment with /test benchmark fullreport
|
Pinging @elastic/security-service-integrations (Team:Security-Service Integrations) |
muthu-mps
left a comment
There was a problem hiding this comment.
As we make the change across different AWS integrations where we have the max_number_of_messages input. The cloudfront logs has not been updated here. Do you consider updating cloudfront_logs as well?
@muthu-mps Good catch! Thank you!!! I just updated it in the new commit. |
💚 Build Succeeded
History
|
|
|
Package aws - 2.22.1 containing this change is available at https://epr.elastic.co/search?package=aws |
|
Package aws_logs - 1.3.1 containing this change is available at https://epr.elastic.co/search?package=aws_logs |




Proposed commit message
This PR is to update the documentation for
max_number_of_messagesto inform users to be cautious when using a large value for this var.Checklist
changelog.ymlfile.Author's Checklist