CSPM: add cloud connectors support#11663
Conversation
🚀 Benchmarks reportTo see the full report comment with |
6c2edb5 to
ba48abd
Compare
There was a problem hiding this comment.
do we want this change in 8.16 ? as we didn't test 8.16 with this change, maybe it would be safer to have in in 1.12.x?
There was a problem hiding this comment.
You are right; I forgot we still need to bump to 8.17.
This means I should merge after we bump the stable 1.11.0 to create the 1.12.0-preview1. (otherwise, it would be a bit more complicated to produce the stable 1.11.0 release with a backport branch).
packages/cloud_security_posture/data_stream/findings/agent/stream/aws.yml.hbs
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
PROJECT_ID refers to the id of a Serverless Project. This maybe a confusing name to include the deployment id. Perhaps another slightly more generic name ELASTIC_SERVICE_ID? Wdyt?
There was a problem hiding this comment.
Sure I will update accordingly.
ba48abd to
52dc54a
Compare
There was a problem hiding this comment.
should we prefix aws.support_cloud_connectors here?
There was a problem hiding this comment.
That's a good question; I am not entirely sure. I thought that since, hierarchy-wise, we are under the input: cloud beat/cis_aws object, it's not really needed. But I will try to find out why we have the aws. prefix in the aws.credentials.type and in aws.account_type.
There was a problem hiding this comment.
For consistency. All other providers have been using prefixes, so we use them for AWS as well. Technically, it also helps avoid mistakes when creating policy via API.
There was a problem hiding this comment.
Thanks @kubasobon! I added aws. prefix in supports_cloud_connectors as well.
52dc54a to
1479acd
Compare
|
@Omolola-Akinleye: note that the |
💚 Build Succeeded
History
cc @moukoublen |
|
kubasobon
left a comment
There was a problem hiding this comment.
Thanks for adding the prefixes
|
Package cloud_security_posture - 1.12.0-preview01 containing this change is available at https://epr.elastic.co/package/cloud_security_posture/1.12.0-preview01/ |
* CSPM: add cloud connectors support * renames * pre release bump * Update packages/cloud_security_posture/manifest.yml Co-authored-by: Orestis Floros <orestisflo@gmail.com> * rename ELASTIC_SERVICE_ID to RESOURCE_ID * add aws. prefix in supports_cloud_connectors --------- Co-authored-by: Orestis Floros <orestisflo@gmail.com>
* CSPM: add cloud connectors support * renames * pre release bump * Update packages/cloud_security_posture/manifest.yml Co-authored-by: Orestis Floros <orestisflo@gmail.com> * rename ELASTIC_SERVICE_ID to RESOURCE_ID * add aws. prefix in supports_cloud_connectors --------- Co-authored-by: Orestis Floros <orestisflo@gmail.com>




Proposed commit message
Add new template URL for cloudformation creates the cloud connectors remote role.
Add a new bool variable indicating that cloud connectors are used in the integration. Cloudbeat should parse this boolean.
Checklist
changelog.ymlfile.Author's Checklist
How to test this PR locally
Related issues
Screenshots