You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The kube-bench pod when running the latest (v0.7.1) version of the aquasec/kube-bench image errors
failed to output to ASFF: finding publish failed: not found, ResolveEndpointV2
deployed via job-eks-asff.yaml
Does not occur with previous version v0.6.19
How did you run kube-bench?
kubectl apply -f job-eks-asff.yaml
What happened?
failed to output to ASFF: finding publish failed: not found, ResolveEndpointV2
What did you expect to happen:
to have output like
2024/02/12 14:39:29 Number of findings that were successfully imported:3
Environment
v0.7.1
v1.26.12-eks-5e0fdde
Anything else you would like to add:
Think it is related to aws/aws-sdk-go-v2#2370 , it mentions a date in November 2023 so I decided to try a older kube-bench container image (v.06.19) from October and this image doesn't seem to have any problem.
The text was updated successfully, but these errors were encountered:
Overview
The kube-bench pod when running the latest (v0.7.1) version of the aquasec/kube-bench image errors
failed to output to ASFF: finding publish failed: not found, ResolveEndpointV2
deployed via job-eks-asff.yaml
Does not occur with previous version v0.6.19
How did you run kube-bench?
kubectl apply -f job-eks-asff.yaml
What happened?
failed to output to ASFF: finding publish failed: not found, ResolveEndpointV2
What did you expect to happen:
to have output like
2024/02/12 14:39:29 Number of findings that were successfully imported:3
Environment
v0.7.1
v1.26.12-eks-5e0fdde
Anything else you would like to add:
Think it is related to aws/aws-sdk-go-v2#2370 , it mentions a date in November 2023 so I decided to try a older kube-bench container image (v.06.19) from October and this image doesn't seem to have any problem.
The text was updated successfully, but these errors were encountered: