Open yruss972 opened 2 years ago
I am facing the same issue, and can confirm that the commands @yruss972 mentions are behaving in the same manner for me.
What other information is needed to help debug this issue?
@yruss972 and @attacus - had the same issue, traced it down to not enough memory on my system to process. Was running in a VM so I upped the allocated mem and presto.
awspx is failing to save the ingested data. I think I've narrowed the issue down to something related to the IAM service ingestion. This works:
awspx ingest --skip-attacks-all --services S3 --skip-types AWS::S3::Object --region us-east-1
This fails:awspx ingest --skip-attacks-all --services IAM --region us-east-1
There is no error message- the ingest command just exists after printing
NOTICE Saving ingested data
and the directory for the .csv files has been created.