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

Support EKS Pod Identities for Signing S3 Bundle Requests #6724

Open
alghanmi opened this issue Apr 26, 2024 · 1 comment
Open

Support EKS Pod Identities for Signing S3 Bundle Requests #6724

alghanmi opened this issue Apr 26, 2024 · 1 comment

Comments

@alghanmi
Copy link

What is the underlying problem you're trying to solve?

Currently, OPA supports AWS Signatures using IAM Roles for Service Accounts (IRSA) in EKS to sign and retrieve bundles. EKS Pod Identities is new way to manage permissions in EKS and would like OPA to add support for it.

Describe the ideal solution

I don't know if this solution is inline with the OPA project policies, but if OPA used the AWS SDK to access S3 an SDK upgrade would have added support for EKS Pod Identities. That said, I understand if the project does not want to uptake the SDK.

Describe a "Good Enough" solution

Similar to OPA's support of IRSA, Pod Identities export the AWS_CONTAINER_AUTHORIZATION_TOKEN_FILE that can be used to retrieve the auth token.

Additional Context

In November 2023, AWS announced EKS Pod Identity which is a a new feature that simplifies Kubernetes applications to obtain AWS IAM permissions. It is in a way the successor to IAM Roles for Service Accounts (IRSA). Many Kubernetes administrators are migrating from IRSA to Pod Identities for its simplified workflow, the ability to share roles across clusters and its support of session tags.

@ashutosh-narkar
Copy link
Member

Adding a new method to provide creds seems fine. Feel free to contribute if you'd like. OPA does not vendor the SDK but you can see the implementations of existing providers for reference. Also the code here might be helpful.

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

No branches or pull requests

2 participants