[Bug]: Prowler gets stuck / fails when running Lambda check against account with LZA #4209
Assignees
Labels
Comments
jfagoagas
added
question
and removed
bug
status/needs-triage
|
Hi @js37 it seems that Prowler is just executing that check. It can take a lot of time if you have a lot of lambdas with a great codebase since Prowler analyzes all the source code in memory while running the check. How many AWS Lambda Functions do you have in that account? Thanks for using Prowler 🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Steps to Reproduce
When running this awslambda check on an account that has Landing Zone Accelerator deployed, Prowler gets stuck.
prowler aws -c awslambda_function_no_secrets_in_codeWhen running in log-level INFO mode, this is the output
When running in log-level debug, the last thing that would print out is
DEBUG: https://awslambda-us-west-2-tasks.s3.us-west-2.amazonaws.com:443 "GET /snapshots/<account ID>/<function name>I have tested this check, and it works on other accounts.
Expected behavior
I expect the scan to complete. The ClientErrors due to have service control polices is fine. I expect the scan to finish with no results if it is due to a permission problem.
Actual Result with Screenshots or Logs
In description above.
How did you install Prowler?
From pip package (pip install prowler)
Environment Resource
Prowler 4.2.4 (You are running the latest version, yay!)
OS used
MacOS
Prowler version
4.2.4
Pip version
24
Context
No response
The text was updated successfully, but these errors were encountered: