elastic / elastic/cloudbeat

Add ELB and ECR image to the EKS cluster deployment

Open
#1,063 0 comments 0 reactions 0 assignees View on GitHub
automation cloudbeat good first issue Team:Cloud Security
Dominant language
Go
Stars
58
Forks
55
Avg merge
9h 9m
Merged PRs (30d)
424

Description

**Motivation**
Currently, we don't have visibility on whether we generate findings for the AWS-related fetchers (ELB/ECR) in the `cis_eks` benchmark.
When our terraform deployment creates the EKS cluster, it does not configure a Load balancer, and the agent image is not pulled from ECR, as a result, findings for ELB and ECR are not being generated.
For example, our long-running env doesn't produce those findings and might cause us to miss degradations in those areas.

**Definition of done**
As part of our terraform deployment:
- [ ] Push an updated image of the agent to a public ECR.
- [ ] Create the EKS cluster with an LB

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.