-
Notifications
You must be signed in to change notification settings - Fork 677
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
Unable to run the cloudsploit scan #2059
Comments
I'm experiencing the same issue. This used to work before, nothing was changed in the configuration files. |
Encountered the same issue with version v3.5.0. Rolled back to v3.4.0 and no issues there. |
Thanks for the feedback, ihan97! Hope the Cloudsploit team fixes the root cause as well. |
I am also getting the same error. For more information, check the blog post at https://a.co/cUPnyil /home/aravind/Tools/cloudsploit/node_modules/aws-sdk/lib/request.js:31
Error [TypeError]: AWS[serviceName] is not a constructor time: 2024-09-10T09:18:39.384Z } Node.js v21.6.1 Tried with the v3.4.0 also, getting the same error |
Hi Team,
While running the scan facing below issue can anyone help on this
$ ./index.js --config /opt/cloudsploit/config.js --json out.json
/ | | | |/ | | | () |
| | | | ___ _ _ | | ( _ __ | | ___ | |
| | | |/ _ | | | |/ ` |_ | ' | |/ _ | | __|
| || | () | || | (| |) | |) | | () | | |
_||___/ _,|_,|___/| ./||___/||_|
| |
|_|
CloudSploit by Aqua Security, Ltd.
Cloud security auditing for AWS, Azure, GCP, Oracle, and GitHub
INFO: Using CloudSploit config file: /opt/cloudsploit/config.js
INFO: Skipping AWS pagination mode
INFO: Determining API calls to make...
INFO: Found 356 API calls to make for aws plugins
INFO: Collecting metadata. This may take several minutes...
(node:34) NOTE: The AWS SDK for JavaScript (v2) will enter maintenance mode
on September 8, 2024 and reach end-of-support on September 8, 2025.
Please migrate your code to use AWS SDK for JavaScript (v3).
For more information, check blog post at https://a.co/cUPnyil
(Use
node --trace-warnings ...
to show where the warning was created)/opt/cloudsploit/node_modules/aws-sdk/lib/request.js:31
throw err;
^
Error [TypeError]: collection[serviceLower][callKey][region].data.concat is not a function
at executorCb (/opt/cloudsploit/collectors/aws/collector.js:154:129)
at /opt/cloudsploit/collectors/aws/collector.js:197:37
at /opt/cloudsploit/node_modules/async/dist/async.js:4620:26
at Response. (/opt/cloudsploit/collectors/aws/collector.js:194:48)
at Request. (/opt/cloudsploit/node_modules/aws-sdk/lib/request.js:367:18)
at Request.callListeners (/opt/cloudsploit/node_modules/aws-sdk/lib/sequential_executor.js:106:20)
at Request.emit (/opt/cloudsploit/node_modules/aws-sdk/lib/sequential_executor.js:78:10)
at Request.emit (/opt/cloudsploit/node_modules/aws-sdk/lib/request.js:686:14)
at Request.transition (/opt/cloudsploit/node_modules/aws-sdk/lib/request.js:22:10)
at AcceptorStateMachine.runTo (/opt/cloudsploit/node_modules/aws-sdk/lib/state_machine.js:14:12) {
code: 'TypeError',
time: 2024-07-03T11:21:13.144Z
}
Node.js v18.19.1
The text was updated successfully, but these errors were encountered: