aws / aws/containers-roadmap

[EKS/Fargate] [request]: Show pod's security group in AWS Management Console

Open
#1,821 0 comments 2 reactions 0 assignees View on GitHub
EKS Fargate 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**
What do you want us to build?
It would be nice if I were able to see and edit pod's security groups, which is running on Fargate.
The only way to edit security group of Fargate pods was to use the way demonstrated in [this document](https://docs.aws.amazon.com/eks/latest/userguide/security-groups-for-pods.html#sg-pods-example-deployment).

**Which service(s) is this request for?**
Fargate, EKS

**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
I had to edit pod's security group, and didn't know that it was even possible since the attached security group's ID didn't appear in the AWS Managment Console. As mentioned above, [this documentation](https://docs.aws.amazon.com/eks/latest/userguide/security-groups-for-pods.html#sg-pods-example-deployment) was the only way to edit Fargate pod's security group, and it didn't come in handy.

**Are you currently working around this issue?**
Following [this documentation](https://docs.aws.amazon.com/eks/latest/userguide/security-groups-for-pods.html#sg-pods-example-deployment).

Contributor guide

Open the contributing guide

Research direction

Start by reading the linked EKS security-groups-for-pods documentation and comparing it with the current AWS Management Console behavior for Fargate pods. Done means the pod's attached security group is visible and editable in the console; the issue does not name repository files or tests.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, kubernetes
Domain
cloud, infrastructure
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.