Uri Weisman

> Missed that, thanks @eyalkraft I've also noticed after the merge from upstream that the section of filling in AWS credentials is missing @uri-weisman, did you notice that? It is...

@elasticmachine merge upstream

@elasticmachine merge upstream

The CSP team finds it useful as well, we run a go binary inside an elastic agent (container) and wish to collect the host's proc info.

@andrewkroh - thank you for the quick response. > IIUC, looking at 2.6.23 (the earliest kernel supported by Go) the two architectures that do not use 100 HZ are alpha...

@thbkrkr - can someone from your team please review my PR?

> I deployed the manifest, connected to `/app/security/cloud_security_posture/dashboard` and it doesn't seem configured? thank you for the review! have you installed the KSPM integration?

@eyalkraft IMO, it would be reasonable to include both the volumes and instance identifiers to assist users in correlating resources at the desired level. The `resource` object should contain all...

@eyalkraft, I wasn't aware of this requirement, but it seems like a useful feature. However, our benchmark for AWS CIS only includes a single rule for EC2/EBS (2.2.1), so I'm...

@nick-alayil - I don't think that an ECS `resource` schema exists today. Those are the supported ecs [schemas](https://www.elastic.co/guide/en/ecs/current/ecs-field-reference.html#ecs-field-reference).