Unable to run the cloudsploit scan

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

Start by reproducing the scan with ./index.js --config /opt/cloudsploit/config.js --json out.json on Node.js 18. Inspect collectors/aws/collector.js around lines 154 and 194-197, where the stack trace reports the failure, and identify which AWS response reaches the collector with an unexpected data shape. Done means the scan completes without this TypeError and produces the requested JSON output.

Written by the indexing model from the issue text.