Access entries: clarify whether type EC2 is supported for self-managed nodes (nodeadm InstanceIdNodeName)
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 68/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- aws
- Domain
- documentation
Research direction
Read the Create access entries page and the CreateAccessEntry API reference, then compare their descriptions and generated username table with nodeadm’s “Using instance ID as node name” guidance. Clarify whether EC2 is supported for self-managed nodes without Auto Mode, add its generated username, and state whether an access policy association is required.
Written by the indexing model from the issue text.
Description
Page: Create access entries, plus the type parameter of CreateAccessEntry
Problem
The page describes access entry type EC2 only as "For EKS Auto Mode custom node classes", and its table of generated usernames has no row for EC2. The API reference also says "EC2 (for EKS Auto Mode)" and directs self-managed node roles to EC2_LINUX or EC2_WINDOWS.
The EKS-optimized AMI's nodeadm documentation, Using instance ID as node name, recommends aws eks create-access-entry --type EC2 for self-managed nodes that use the InstanceIdNodeName feature gate. That change came from awslabs/amazon-eks-ami#2392.
Those nodes need the username system:node:{{SessionName}}. EC2_LINUX fixes it to system:node:{{EC2PrivateDNSName}}, and STANDARD rejects system: groups (awslabs/amazon-eks-ami#1821).
Taken together, the two sets of documentation leave it unclear whether EC2 is supported for self-managed nodes outside Auto Mode.
Request
- State whether type
EC2is supported for self-managed EC2 nodes on clusters without Auto Mode, for example nodes using nodeadm'sInstanceIdNodeName. - Add
EC2to the table of generated usernames. - State whether an access policy association, such as
AmazonEKSAutoNodePolicy, is required whenEC2is used outside Auto Mode.
Related question to the nodeadm maintainers: awslabs/amazon-eks-ami#2866
- Dominant language
- Shell
- Stars
- 454
- Forks
- 786
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from awsdocs/amazon-eks-user-guide
-
Platform versions table lags behind actual EKS console (e.g. eks.28 for Kubernetes 1.34 not listed)Open
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
awsdocs/amazon-eks-user-guide#1253 · 1 comment ·
-
Documentation Improvement: Include EKS Platform Version InformationMay be free again @naveenv-devops claimed this 59 days ago, and no pull request is open. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
awsdocs/amazon-eks-user-guide#1249 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
awsdocs/amazon-eks-user-guide#1246 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 68/100
awsdocs/amazon-eks-user-guide#1190 ·
-
NVIDIA DRA driver page: conflicting guidance on Karpenter dynamic provisioningPossibly taken @UhyeongJo claimed this 10 days ago. Open
Difficulty 1/5 Under an hour Newbie friendliness 35/100
awsdocs/amazon-eks-user-guide#1255 ·
All issues in awsdocs/amazon-eks-user-guide
Similar issues
-
Hyprland 0.57: monitor-workspaces reconcile errors on every start and reload when a named workspace exists (workspace.id is nil)Possibly taken @jasasonc claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
priority middle
Difficulty 1/5 Under an hour Newbie friendliness 62/100
KATO-Hiro/AtCoderClans#12940 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
metal3-io/metal3-dev-env#1741 · 1 comment ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 64/100