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
Currently, most IAM roles in eksctl support either referencing existing roles or specifying permission boundaries when creating new ones, but autoModeConfig lacks this capability. This forces customers with permission boundary requirements to:
Create the auto mode node role in advance, outside the cluster creation flow
Reference it via nodeRoleARN in their configuration
Adding a permissionBoundaryARN parameter under autoModeConfig would eliminate this extra step and allow the role to be managed directly through the cluster's CloudFormation stack, maintaining the infrastructure-as-code approach.
Current Limitation
In EKS Auto Mode, when using eksctl to create clusters, the IAM permissions boundary feature that exists for other roles isn't available for autoModeConfig. This creates inconsistency in how IAM roles are managed across the tool.
Proposed Solution
Add a permissionBoundaryARN parameter to the autoModeConfig section of the eksctl ClusterConfig specification. This would allow users to specify an IAM permission boundary ARN that would be applied when creating the auto mode node role.
This enhancement would align with AWS best practices for IAM permissions management and make eksctl more consistent in its handling of IAM roles. It would also make it easier for organizations that use permission boundaries as part of their security controls to adopt EKS Auto Mode.
The text was updated successfully, but these errors were encountered:
Hello amdonov 👋 Thank you for opening an issue in eksctl project. The team will review the issue and aim to respond within 1-5 business days. Meanwhile, please read about the Contribution and Code of Conduct guidelines here. You can find out more information about eksctl on our website
amdonov
pushed a commit
to amdonov/eksctl
that referenced
this issue
Mar 21, 2025
Currently, most IAM roles in eksctl support either referencing existing roles or specifying permission boundaries when creating new ones, but autoModeConfig lacks this capability. This forces customers with permission boundary requirements to:
Adding a permissionBoundaryARN parameter under autoModeConfig would eliminate this extra step and allow the role to be managed directly through the cluster's CloudFormation stack, maintaining the infrastructure-as-code approach.
Current Limitation
In EKS Auto Mode, when using eksctl to create clusters, the IAM permissions boundary feature that exists for other roles isn't available for autoModeConfig. This creates inconsistency in how IAM roles are managed across the tool.
Proposed Solution
Add a permissionBoundaryARN parameter to the autoModeConfig section of the eksctl ClusterConfig specification. This would allow users to specify an IAM permission boundary ARN that would be applied when creating the auto mode node role.
Example implementation in the ClusterConfig:
This enhancement would align with AWS best practices for IAM permissions management and make eksctl more consistent in its handling of IAM roles. It would also make it easier for organizations that use permission boundaries as part of their security controls to adopt EKS Auto Mode.
The text was updated successfully, but these errors were encountered: