Open kneemaa opened 4 years ago
Hi @kneemaa :wave:
thanks for submitting this issue. If you find more resources where this is the case, please let me know. I don't know yet if I can do anything about it, but will let you know.
Also observed the same isssue as @kneemaa with literally the same usecase in mind.
try adding the policy iam:getUser to whichever profile you are running this command from
Error found on certain resource types, so far I've found it for
Our org uses SAML to generate our local STS tokens which we assign to profiles. Some of the resources require a userName to be set.
This would also be needed if we were to run AWSweeper as a container or scheduled task within AWS.
If this isn't possible, I don't mind submitting a PR to update the README