-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
failed to output to ASFF: finding publish failed: not found, ResolveEndpointV2 #1595
Comments
Any update on this? I'm experiencing the same error with the same setup: |
I encountered the same issue while deploying Kube-bench with the latest version. The latest version has some bugs, though I am not sure of the specifics. However, I deployed version 6.19.0, and it is working for me. You can download version 6.19.0 using the command below and follow the steps mentioned in the official documentation. git clone https://github.com/aquasecurity/kube-bench.git --branch v0.6.19 |
git clone https://github.com/aquasecurity/kube-bench.git --branch v0.6.19 |
1 similar comment
git clone https://github.com/aquasecurity/kube-bench.git --branch v0.6.19 |
I wonder if this issue will be fixed. In version v0.8.0 we still see the same error. The root cause might be related to the aws-sdk-go packages as described here: aws/aws-sdk-go-v2#2370 (comment) Thank you. |
A breaking change was introduced in aws-sdk-go-v2. See aws/aws-sdk-go-v2#2370 (comment). Mixing aws-sdk-go-v2 packages from versions before and after the breaking change causes kube-bench to fail. This issue occurs when it attempts to access AWS Security Hub. Addressed issue: aquasecurity#1595 Supersedes bot PR: aquasecurity#1689 Besides upgrading to latest SDK version, some variable types need to be adapted.
A breaking change was introduced in aws-sdk-go-v2. See aws/aws-sdk-go-v2#2370 (comment). Mixing aws-sdk-go-v2 packages from versions before and after the breaking change causes kube-bench to fail. This issue occurs when it attempts to access AWS Security Hub. Addressed issue: #1595 Supersedes bot PR: #1689 Besides upgrading to latest SDK version, some variable types need to be adapted.
A breaking change was introduced in aws-sdk-go-v2. See aws/aws-sdk-go-v2#2370 (comment). Mixing aws-sdk-go-v2 packages from versions before and after the breaking change causes kube-bench to fail. This issue occurs when it attempts to access AWS Security Hub. Addressed issue: aquasecurity#1595 Supersedes bot PR: aquasecurity#1689 Besides upgrading to latest SDK version, some variable types need to be adapted.
Overview
I am trying to integrate AWS security Hub and EKS , and I've come across the following issue. Would you happen to have any suggestions on how to resolve it? Your assistance would be greatly appreciated. Thank you!
Here are the details regarding the error encountered.
failed to output to ASFF: finding publish failed: not found, ResolveEndpointV2
How did you run kube-bench?
[Please specify exactly how you ran kube-bench, including details of command parameters and/or job file that you used to run it]
What happened?
What did you expect to happen:
I'm expecting that the pods should run smoothly and push the results to AWS Security Hub without encountering these errors.
Environment
[What is your version of kube-bench? (run
kube-bench version
)]latest -> v0.7.2
[What is your version of Kubernetes? (run
kubectl version
oroc version
on OpenShift.)]EKS 1.29
The text was updated successfully, but these errors were encountered: