-
Notifications
You must be signed in to change notification settings - Fork 102
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
IndexError: list index out of range error every time its run with additional flags of --services or --skip-types #41
Comments
Hi @thomas-devoss, Thanks for reporting the issue! To be honest with you, I'm a bit stumped - I've encountered the issue myself and believe its been fixed in the Would you mind pulling the changes, rerunning |
Sure I can do that today and get back with you, thanks! |
Hi there, I am also seeing the same (or similar issues) trying both I've attached the traceback below from attempting to run :
This is on macOS Catalina.
Thanks |
Hey @rpigu-i , Thanks for reporting this issue - it looks like an issue with an empty label (probably from parsing an unknown principal in an assume role policy document). Hopefully, this last commit fixes it. Would you mind running |
Every time I run awspx with --skip-types or the --services flag, I get the following error:
This happens when it gets to 'resolving policy information'
This does not happen when I just run ./awspx ingest however when I run it like this it will not show any connections/attacks etc in the web gui.
Running with the following flags:
./awspx ingest --skip-types "AWS::S3::Object"
./awspx ingest --services EC2, Lambda, IAM
This is running on a MacOS system, inside the docker container pulled down 2 weeks ago (right around the 10th of January)
The text was updated successfully, but these errors were encountered: