Skip to content
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

fix(checks): AVD-AWS-0034 enhanced container insights #332

Conversation

MichaelFoleyFZ
Copy link

Replaces the current ContainerInsightsEnabled boolean attribute on the ECS cluster settings with ContainerInsightsMode. Container Insights now supports three possible values, enabled, disabled and enhanced (https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_ClusterSetting.html)

The enhanced mode is what is recommended by AWS now to get further metrics and details but has been separted from enable/disable due to its cost.

@CLAassistant
Copy link

CLAassistant commented Jan 30, 2025

CLA assistant check
All committers have signed the CLA.

@simar7
Copy link
Member

simar7 commented Jan 31, 2025

Hmm interesting. So what happens to the old value, was it deprecated?

@MichaelFoleyFZ
Copy link
Author

MichaelFoleyFZ commented Jan 31, 2025

Hmm interesting. So what happens to the old value, was it deprecated?

So the containerInsights setting in the api was always a string but it was just enabled/disabled so fit with being setup as a binary value.

But to add enhanced container insights AWS just added a third possible string value enhanced to the same containerInsights setting

In the case of trivy I removed the old value as I wasn't sure what the stance was on a change like that.

@nikpivkin
Copy link
Contributor

Hi @MichaelFoleyFZ !

The rule still checks that Container Insights is disabled. So can't we therefore process the string value on the Trivy side and export only the boolean value?

@MichaelFoleyFZ
Copy link
Author

Will swap the sledge hammer for a screw driver

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants