Describe the bug
When running pmapper --profile profile_name graph create, I eventually get stuck at the Stuck at Generating Edges based on lambda data step.
I think it's because my user does not have the privilege to perform lambda:ListFunctions. I get the following error:
2022-04-14 20:46:43-0400 | DEBUG | principalmapper.graphing.lambda_edges | Exception details: An error occurred (AccessDeniedException) when calling the ListFunctions operation: User: arn:aws:sts::<AWS_ACCOUNT_ID>:<assumed-role/AWS_ACCOUNT_ROLE>/<AWS_ACCOUNT_USER> is not authorized to perform: lambda:ListFunctions on resource: * with an explicit deny in a service control policy
To Reproduce
Steps to reproduce the behavior, please include information on suspected users/roles that are the source of the issue when possible:
Use a AWS profile that does not have the ability to ListFunction.
Run the aforementioned command.
See that it gets hung at the Generating Edges based on Lambda data..
Expected behavior
It should not get stuck. If you need to quit the program, that would be better.
Describe the bug When running
pmapper --profile profile_name graph create
, I eventually get stuck at theStuck at Generating Edges based on lambda data
step.I think it's because my user does not have the privilege to perform
lambda:ListFunctions
. I get the following error:2022-04-14 20:46:43-0400 | DEBUG | principalmapper.graphing.lambda_edges | Exception details: An error occurred (AccessDeniedException) when calling the ListFunctions operation: User: arn:aws:sts::<AWS_ACCOUNT_ID>:<assumed-role/AWS_ACCOUNT_ROLE>/<AWS_ACCOUNT_USER> is not authorized to perform: lambda:ListFunctions on resource: * with an explicit deny in a service control policy
To Reproduce Steps to reproduce the behavior, please include information on suspected users/roles that are the source of the issue when possible:
Generating Edges based on Lambda data.
.Expected behavior It should not get stuck. If you need to quit the program, that would be better.