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
My 3.11.0 ParallelCluster deployment failed due to insufficient AWS permissions for a Lambda role created by the API stack. The Lambda function requires the permission 'elasticloadbalancing:DescribeTags', but this permission is not included in the policy configuration.
Most likely, this issue was caused by changes to the permissions in the 'cloudformation/policies/parallelcluster-policies.yaml' file since ParallelCluster version 3.10.1 where the elasticloadbalancing:Describe* permission was included.
The deployment succeeds when there are no login nodes in the cluster configuration, but fails when the login nodes section is included.
kondakovm
changed the title
[3.11] elasticloadbalancing:DescribeTags permission is required to run a cluster with login nodes
[3.11] elasticloadbalancing:DescribeTags permission missing when run a cluster with login nodes
Oct 20, 2024
kondakovm
changed the title
[3.11] elasticloadbalancing:DescribeTags permission missing when run a cluster with login nodes
[3.11] elasticloadbalancing:DescribeTags permission is missing when run a cluster with login nodes
Oct 20, 2024
My 3.11.0 ParallelCluster deployment failed due to insufficient AWS permissions for a Lambda role created by the API stack. The Lambda function requires the permission 'elasticloadbalancing:DescribeTags', but this permission is not included in the policy configuration.
Most likely, this issue was caused by changes to the permissions in the 'cloudformation/policies/parallelcluster-policies.yaml' file since ParallelCluster version 3.10.1 where the
elasticloadbalancing:Describe*
permission was included.The deployment succeeds when there are no login nodes in the cluster configuration, but fails when the login nodes section is included.
The cluster configuration:
Lambda logs for evidence:
The text was updated successfully, but these errors were encountered: