amazon-archives/aws-security-benchmark

Not handling the caching of the cred report

Opened this issue · 3 comments

After detecting an IAM user not compliant, if you delete it, the execution of the benchmark will fail. The root cause is that the cred report is cached for 4h. But multiple functions in the benchmark go through the cred report user list assuming that all the users exist.

👍

Hi, can you provide what control fails and I will add proper error handling.
The credential report cannot be generated more then once per 4h so the controls themselves should handle removed credentials.

1.2, 1.3, 1.4. I'd used
Try:

Except:
continue