1 Answer
- Newest
- Most votes
- Most comments
0
Could you try disabling and re-enabling the feature. According to this repost answer a similar issue got resolved after disabling and then re-enabling.
answered 9 months ago
I tried disabling and enabling Lambda scannings, but still there is remarkable number (34 of 93 total) of Lambdas, which are not scanned because of "Internal error"
Relevant content
- asked a month ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 4 months ago
- AWS OFFICIALUpdated 2 years ago
To obtain efficient support, can you display those error messages?
Only message Inspector gives on these Lambdas is: "Internal error Inspector has encountered an internal error for this resource. Inspector service will automatically resolve the issue and resume the scanning. No action required from the user."