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

Limit worker-node IAM Role permissions in CAPA #3795

Open
2 tasks
T-Kukawka opened this issue Dec 4, 2024 · 0 comments
Open
2 tasks

Limit worker-node IAM Role permissions in CAPA #3795

T-Kukawka opened this issue Dec 4, 2024 · 0 comments
Assignees
Labels
provider/cluster-api-aws Cluster API based running on AWS team/phoenix Team Phoenix

Comments

@T-Kukawka
Copy link
Contributor

T-Kukawka commented Dec 4, 2024

As a customer i would like to have as limited permissions of the IAM role attached to the worker nodes as possible. Currently if Pod has access to the EC2 instance metadata, it will be able to assume the instance's attached IAM role. Hence with this role it is granted permissions that the nodes have. The behavior does not depend on the IMDS version and can happen with both, v1 and v2.

At the current stage the capa-iam-operator configures the permissions as following: https://github.com/giantswarm/capa-iam-operator/blob/master/pkg/iam/nodes_template.go. The set is very broad and it is definitely advised to narrow it down, because currently it raises security concerns that are understandable. We have to remember about such workloads as ebs-csi-driver or aws-cloud-controller-manager which might require broader permissions due to their underlying processes.

Option to narrow down the permissions is the safest approach which should not affect the actual workloads of customers running on the clusters. The topic of accessing the instance metadata itself will be taken up separately in following issue: #3796

Acceptance criteria:

  • Perform a deep dive by removing ALL permissions granted to the worker nodes IAM role and identify the actually required permissions, such that the nodes are fully operational with no impact on workloads running in the cluster.
  • Apply new, narrowed down permissions set in capa-iam-operator
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
provider/cluster-api-aws Cluster API based running on AWS team/phoenix Team Phoenix
Projects
Status: Inbox 📥
Development

No branches or pull requests

2 participants