Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cloud Policies missing #220

Open
jeason81 opened this issue Apr 18, 2024 · 1 comment
Open

Cloud Policies missing #220

jeason81 opened this issue Apr 18, 2024 · 1 comment
Assignees

Comments

@jeason81
Copy link

I am attempting to setup Kubescape Operator in an EKS environment but have been unsuccessful in determining what AWS permissions are required when specifying the cloudProviderMetadata.awsIamRoleArn section of the Helm chart. I found the documentation lacking for all Cloud Providers but was able to find this: https://hub.armosec.io/recipes/setup-aws-iam-authorization-of-in-cluster-installation-of-kubescape-in-eks. However, it appears this may be outdated as the Helm chart requires only a single ARN and the recipe creates two service accounts with their own policies. Additionally, the recipe specifies the --set createKubescapeServiceAccount=false parameter when doing the Helm install which does not exist in the current Helm chart.

Is it possible to get documentation on what is required for creating the AWS accounts/permissions needed for use with Kubescape Operator?

@Oshratn
Copy link
Contributor

Oshratn commented Jul 25, 2024

@matthyx this seems like a documentation bug. Please add it to the board.

@matthyx matthyx moved this to Triage in Kubescaping Aug 18, 2024
@matthyx matthyx moved this from Triage to Accepted in Kubescaping Sep 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Accepted
Development

No branches or pull requests

2 participants