Replies: 1 comment 1 reply
-
Hi @ckuethe - good question! A good "getting started" answer is that a read-only/security audit role is enough to experiment with policies - assuming that you're running policies with no actions and/or using the |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Ask your question
I'm starting to experiment with cloud custodian and would like to know what permissions I should grant for each of my cloud providers in order to simply audit my clouds.
I did look at all the documentation, especially the getting started sections (eg. https://cloudcustodian.io/docs/gcp/gettingstarted.html and https://cloudcustodian.io/docs/aws/gettingstarted.html), for a list of permissions and roles that each provider requires. Logging in as me and using my session isn't really a great option.
In contrast, other tools such as ScoutSuite and CloudSploit do list the permissions required.
Policy
No response
Relevant log/traceback output
No response
Beta Was this translation helpful? Give feedback.
All reactions