Skip to content

Support additional access entry types EC2 and HYPERPOD_LINUX #3350

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

Closed
1 task done
lorengordon opened this issue Apr 25, 2025 · 1 comment
Closed
1 task done

Support additional access entry types EC2 and HYPERPOD_LINUX #3350

lorengordon opened this issue Apr 25, 2025 · 1 comment

Comments

@lorengordon
Copy link
Contributor

Description

The CreateAccessEntry API supports additional types that the module currently does not allow, in particular EC2 and HYPERPOD_LINUX.

See: https://docs.aws.amazon.com/eks/latest/APIReference/API_CreateAccessEntry.html#AmazonEKS-CreateAccessEntry-request-type

At the moment, specifying on of the disallowed types results in a STANDARD access entry, which does not work when configuring the respective features.

For example, creating a custom node class for use with EKS Auto Mode requires an access entry of type EC2, https://docs.aws.amazon.com/eks/latest/userguide/create-node-class.html#auto-node-access-entry.

  • ✋ I have searched the open/closed issues and my issue is not listed.

Versions

  • Module version [Required]: 20.36.0

Reproduction Code [Required]

  access_entries = {
    auto_mode = {
      principal_arn = module.cluster.node_iam_role_arn
      type          = "EC2"

      policy_associations = {
        AmazonEKSAutoNodePolicy = {
          policy_arn = "arn:aws:eks::aws:cluster-access-policy/AmazonEKSAutoNodePolicy"
          access_scope = {
            type = "cluster"
          }
        }
      }
    }
  }
@lorengordon
Copy link
Contributor Author

Nope, that wasn't it. My input wrapper was trashing the type, so it was picking up the default from from the try expression.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant