aws / aws/containers-roadmap

[EKS] [Node Group]: Give EC2 instances a Name tag

Open
#781 32 comments 422 reactions 0 assignees View on GitHub
EKS EKS Managed Nodes Proposed
Dominant language
Shell
Stars
5.4k
Forks
334
PR merge metrics
No merged PRs in 30d

Description

### Community Note

* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request
* Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
* If you are interested in working on this issue or have submitted a pull request, please leave a comment

**Tell us about your request**
Add Name tag to EKS nodegroup instances, based on the node group name.

**Which service(s) is this request for?**
EKS node groups.

**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
Give EKS EC2 node group instances a Name to make them easier to identify, similar to ECS instances.

**Are you currently working around this issue?**
Manually adding Name tag.

Contributor guide

Open the contributing guide

Research direction

No source files, tests, or implementation entry points are identified in the issue. Start by reviewing the EKS node-group instance tagging path and related ECS tagging behavior, then confirm the expected AWS ownership and validation approach. Done means EKS node-group EC2 instances receive a Name tag derived from the node group name.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, kubernetes
Domain
cloud, infrastructure
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.