Adding EKS input type to the cloud security posture integration #3619
Conversation
💚 Build Succeeded
Expand to view the summary
Build stats
Test stats 🧪
🤖 GitHub commentsTo re-run your PR in the CI, just comment with:
|
| @@ -1,6 +1,28 @@ | |||
| title: "Findings" | |||
| type: logs | |||
| streams: | |||
| - input: cloudbeat | |||
| - input: cloudbeat/vanilla | |||
There was a problem hiding this comment.
Need to verify before merging it, that the integration is part of the ELK release candidate
There was a problem hiding this comment.
It is not part of the official release but we set the integration to work only with 8.4 version so no worries regrading it
There was a problem hiding this comment.
Attached here is the backward compatibility matrix as a reminder, indeed that makes that incompatible with 8.3.0 agents.
As you mentioned, this version is available from kibana.version 8.4.0 only, so no issue here.
🌐 Coverage report
|
| @@ -1,6 +1,28 @@ | |||
| title: "Findings" | |||
| type: logs | |||
| streams: | |||
| - input: cloudbeat | |||
| - input: cloudbeat/vanilla | |||
There was a problem hiding this comment.
Attached here is the backward compatibility matrix as a reminder, indeed that makes that incompatible with 8.3.0 agents.
As you mentioned, this version is available from kibana.version 8.4.0 only, so no issue here.
kfirpeled
added
the
Team:Cloud Security
What does this PR do?
This PR is enhancing the current Cloud security posture integration by adding another input type that supports collecting findings against an EKS cluster.
The new input type defines new input fields AKA the AWS credentials that should be sent as part of creating the integration.
Checklist
changelog.ymlfile.Related issues