Skip to content
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

Request for Adding Amazon EKS Pod Identity Add-on Support #200

Closed
Pjv93 opened this issue Jan 25, 2024 · 3 comments
Closed

Request for Adding Amazon EKS Pod Identity Add-on Support #200

Pjv93 opened this issue Jan 25, 2024 · 3 comments
Labels

Comments

@Pjv93
Copy link
Collaborator

Pjv93 commented Jan 25, 2024

**Is your feature request related to a problem?
I would like to request the addition of support for the Amazon Elastic Kubernetes Service (EKS) Pod Identity addon in the EKS Anywhere Addons repository. The Amazon EKS Pod Identity addon is a valuable feature that allows applications running on Amazon EKS clusters to securely obtain AWS Identity and Access Management (IAM) credentials. This capability is essential for applications that need to interact with AWS services, such as Amazon S3, DynamoDB, or AWS Secrets Manager, while running within Kubernetes pods.

Describe the solution you'd like
Adding support for the Amazon EKS Pod Identity addon would greatly benefit users who deploy applications on EKS Anywhere clusters. This feature enables applications to assume IAM roles based on annotations assigned to Kubernetes service accounts, providing fine-grained access control to AWS resources. This is particularly valuable in scenarios where applications need to access AWS resources securely without relying on static IAM credentials.

Additional context
Amazon EKS Pod Identity: A New Way for Applications on EKS to Obtain IAM Credentials

Amazon EKS Pod Identity Documentation

@Pjv93 Pjv93 closed this as completed Jan 25, 2024
@elamaran11 elamaran11 reopened this Jan 25, 2024
@elamaran11
Copy link
Contributor

@Pjv93 Why did we close this?

Copy link

This issue has been automatically marked as stale because it has been open 60 days
with no activity. Remove stale label or comment or this issue will be closed in 10 days

@github-actions github-actions bot added the stale label Apr 25, 2024
Copy link

Issue closed due to inactivity.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Jun 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants