aquasecurity / aquasecurity/cloudsploit
./index.js execution issue
- Dominant language
- JavaScript
- Stars
- 3.8k
- Forks
- 751
- Avg merge
- 11d 9h
- Merged PRs (30d)
- 3
Description
Hi Team,
Build Cloudsploit in Ubuntu Server and trying to execute the scan for our AWS account.
I have copied the config file and hardcoded my secret key and access key in config.js file as follows, but looks like my credentails is not recognizing by cloudsploit.
Please let me know if i misconfigured anything here or need any additional configurations.
---------------------------
CloudSploit config file
module.exports = {
credentials: {
aws: {
// OPTION 1: If using a credential JSON file, enter the path below
// credential_file: '/path/to/file.json',
// OPTION 2: If using hard-coded credentials, enter them below
access_key: process.env.AWS_ACCESS_KEY_ID || '***************************',
secret_access_key: process.env.AWS_SECRET_ACCESS_KEY || '****************',
// session_token: process.env.AWS_SESSION_TOKEN || '',
// plugins_remediate: ['bucketEncryptionInTransit']
-----------------------------------------------------------------

Contributor guide
Research direction
Start with ./index.js and config.js, then reproduce the scan execution on Ubuntu using the credential configuration shown in the issue. Done means CloudSploit recognizes the configured AWS credentials and proceeds with the account scan; the issue does not identify a failing test or a more specific code location.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, javascript
- Domain
- cli, cloud, security
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100