Error: Nothing to report

I get this when trying to run cloudsploit security scan on my aws instance.
I've set credentials within the config.js file using access_key,
secret_access_key and session_token

./index.js --config ./config.js

_____ _ _ _____ _ _ _
/ ____| | | |/ ____| | | (_) |
| | | | ___ _ _ __| | (___ _ __ | | ___ _| |_
| | | |/ _ \| | | |/ _` |\___ \| '_ \| |/ _ \| | __|
| |____| | (_) | |_| | (_| |____) | |_) | | (_) | | |_
\_____|_|\___/ \__,_|\__,_|_____/| .__/|_|\___/|_|\__|
| |
|_|

CloudSploit by Aqua Security, Ltd.
Cloud security auditing for AWS, Azure, GCP, Oracle, and GitHub

INFO: Using CloudSploit config file: ./config.js
INFO: Skipping AWS pagination mode
INFO: Determining API calls to make...
INFO: Found 159 API calls to make for aws plugins
INFO: Collecting metadata. This may take several minutes...
INFO: Metadata collection complete. Analyzing...
INFO: Analysis complete. Scan report to follow...
ERROR: Nothing to report...
ERROR: Nothing to report...
ERROR: Nothing to report...
ERROR: Nothing to report...
ERROR: Nothing to report...
ERROR: Nothing to report...
ERROR: Nothing to report...
ERROR: Nothing to report...
ERROR: Nothing to report...
ERROR: Nothing to report...

Start by reviewing ./config.js and the ./index.js --config ./config.js command, then reproduce the scan using the reported credentials and log output. Trace the path after metadata collection and analysis to determine why the scan produces no report; done means the cause is documented and the command either emits the expected report or a useful error.

Written by the indexing model from the issue text.