-
Couldn't load subscription status.
- Fork 25.6k
Add aws.config source indices to kibana_system role permissions #128350
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
|
Pinging @elastic/es-security (Team:Security) |
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
Reasoning:
Although we generally would not grant the system user access to data indexes, an exception is made for logs-* (documented here) as it is a known collision pattern.
|
@kc13greiner, is there anything that should be done to automatically create all the backport PRs? cc: @maxcold |
|
@kcreddy I am not sure how the es repo labels work. The |
@kc13greiner can you please tag someone to assist with this issue, considering the public release is tomorrow for these branches? |
|
@slobodanadamovic, this PR is very similar to #124074 which you approved previously. But the backport PRs aren't getting created here even though cc: @maxcold |
@slobodanadamovic, Actually I added this label right after creating the PR, even before the review: #128350 (comment) |
I missed that. Sorry! Not sure why it did not work. The @elastic/es-delivery team might help diagnosing this. In any case, I think you'll have to use the backport tool locally or backport the PR manually. There is no way to trigger backporting after the PR got merge. Given that this happens from time to time it would be nice to have the ability to manully trigger backport, e.g. via |
Thanks for the quick help ❤️ I will check the backport tool and create PRs.
Strongly agree with this 💯 |
💔 Some backports could not be created
Manual backportTo create the backport manually run: Questions ?Please refer to the Backport tool documentation |
…tic#128350) Adding `logs-aws.config-*` data stream indices to the `kibana_system` privileges. This is required for the latest transform to work. Related: - elastic/integrations#13830 (comment) (cherry picked from commit 169527f)
…tic#128350) Adding `logs-aws.config-*` data stream indices to the `kibana_system` privileges. This is required for the latest transform to work. Related: - elastic/integrations#13830 (comment) (cherry picked from commit 169527f)
…tic#128350) Adding `logs-aws.config-*` data stream indices to the `kibana_system` privileges. This is required for the latest transform to work. Related: - elastic/integrations#13830 (comment) (cherry picked from commit 169527f)
@slobodanadamovic, I created backport PRs using the backport tool. Also there is an error for |
…tic#128350) Adding `logs-aws.config-*` data stream indices to the `kibana_system` privileges. This is required for the latest transform to work. Related: - elastic/integrations#13830 (comment) (cherry picked from commit 169527f)
💚 All backports created successfully
Questions ?Please refer to the Backport tool documentation |
) (#128443) Adding `logs-aws.config-*` data stream indices to the `kibana_system` privileges. This is required for the latest transform to work. Related: - elastic/integrations#13830 (comment) (cherry picked from commit 169527f)
) (#128446) Adding `logs-aws.config-*` data stream indices to the `kibana_system` privileges. This is required for the latest transform to work. Related: - elastic/integrations#13830 (comment) (cherry picked from commit 169527f)
) (#128444) Adding `logs-aws.config-*` data stream indices to the `kibana_system` privileges. This is required for the latest transform to work. Related: - elastic/integrations#13830 (comment) (cherry picked from commit 169527f)
) (#128460) Adding `logs-aws.config-*` data stream indices to the `kibana_system` privileges. This is required for the latest transform to work. Related: - elastic/integrations#13830 (comment) (cherry picked from commit 169527f)
…R) workflow (#15230) aws: Add transforms to Config and Inspector data streams for extended protections (CDR) workflow. - Add latest transform to Config and Inspector data streams to help with Cloud Native Vulnerability Management (CNVM)[1] and Cloud Security Posture Management (CSPM)[2] workflows. - Add ILM policy to AWS Config as it does full sync every interval. - Update minimum kibana version to "^8.19.0 || ^9.1.0" to ensure necessary permissions for transform[3]. - Re-add 3.14.2 changelog entry as it is overwritten in VPC Flow PR[4]. - Skip system tests for securityhub* data streams to avoid fleet health degradation due to empty template values by httpjson. This is fixed in 8.19.4 and 9.1.4 by beats#45810[5] and beats#46332[6]. This skip can be removed when the stack version is upgraded to ones containing the fix. [1] https://www.elastic.co/guide/en/security/current/vuln-management-overview.html [2] https://www.elastic.co/docs/solutions/security/cloud/cloud-security-posture-management [3] elastic/elasticsearch#128350 [4] #15077 [5] elastic/beats#45810 [6] elastic/beats#46332
Adding
logs-aws.config-*data stream indices to thekibana_systemprivileges. This is required for the latest transform to work.Related:
Similar to #124074