You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 13, 2024. It is now read-only.
Is this really necessary or is there a more restrictive permission set that could accomplish the same?
"arn:aws:iam::aws:policy/service-role/AWSLambdaVPCAccessExecutionRole" It seems to me that GuardDuty doesn't need to do anything with the VPC. It should just receive the guard duty message as JSON and then post it on to slack. Thoughts?
The text was updated successfully, but these errors were encountered:
Is this really necessary or is there a more restrictive permission set that could accomplish the same?
"arn:aws:iam::aws:policy/service-role/AWSLambdaVPCAccessExecutionRole" It seems to me that GuardDuty doesn't need to do anything with the VPC. It should just receive the guard duty message as JSON and then post it on to slack. Thoughts?
The text was updated successfully, but these errors were encountered: