Importing Custom JSON File

[Nebula-Ninjas]

Dear OpenCSPM,

I am rather new to this Docker stuff, and my question may be just my lack of knowledge around the platform. In short, when I create the custom JSON file, extract to the folder specified for OpenCSPM to import. I then attempt to reload the data (via web console / docker-compose down/up) I get the following error.

worker_1 | Warning: no Backup loader defined for asset type: protected_resource
worker_1 | Loader job failed - NameError uninitialized constant AWSLoader::ApplicationAutoScaling (/app/app/jobs/lib/loader/asset/loaders/aws_loader/_resource_loader.rb:25:in const_get') worker_1 | Runner job failed - NameError uninitialized constant AWSLoader::ApplicationAutoScaling (/app/app/jobs/lib/loader/asset/loaders/aws_loader/_resource_loader.rb:25:in const_get')
worker_1 | I, [2021-04-21T14:06:28.283442 #1] INFO -- : [ActiveJob] [RunnerJob] [f82dc9b3-19f5-485b-b664-f60a937113ed] Performed RunnerJob (Job ID: f82dc9b3-19f5-485b-b664-f60a937113ed) from Sidekiq(default) in 44876.54ms
worker_1 | 2021-04-21T14:06:28.295Z pid=1 tid=gp5k0oly1 class=RunnerJob jid=535e242bd81a6098d34bbb62 elapsed=44.947 INFO: done

I hope this is just my lack of knowledge around the dependencies of the tool and you all can provide some insight as to remedy.

On another note, tool is AWESOME and one of the easiest to get up and working from other tools I've used. Thank you all for creating this and hopefully my issue is easily resolve with a few commands on my part.

Thanks in advance!

William

[joshlarsen]

Hi William. This actually a bug. We've opened issue 153 for it. We'll work on a fix shortly.

Thanks!

[joshlarsen]

Let me know the flags you are running aws_recon with. If the output file is large, you may have to use the file output options as opposed to redirecting stdout.

[Nebula-Ninjas]

AWS_PROFILE=coda-dev /gems/bin/aws_recon -j
-r global,us-east-1
-f custom > output.json

Posting a potential issue on the aws_recon repo now as well as I think I may have found another issue but will let you confirm.

Sincerely,

William

[Nebula-Ninjas]

@joshlarsen giving an update:

I was finally able to get the JSON file to load after removing some services that are not fully supported (lambda's w/ vpc_id, DirectoryService). I'll post to my other thread on my experiences with aws_recon in hopes it will help.

Last question I have (for the time being..LOL) is do you guys have an option to export to CSV? I have not checked and will do so in a bit, just wanted to ask while it was fresh on my brain.

Thank you for all the direction and assistance and let me know if you need me to test anything out for you all. More than happy to do so.

[joshlarsen]

Hi William,

There is no CSV export option as of yet. Where would you want to see that? In the controls list view?

[Nebula-Ninjas]

@joshlarsen where ever it would be the easiest to add the option. It would be a bonus if when exported it listed the issues with the severity rating.

Thanks in advance,

William