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

KCL consumer on kubernetes does not pick up IAM role via serviceAccount. #79

Open
yogesh8177 opened this issue Jan 29, 2021 · 1 comment · May be fixed by #275
Open

KCL consumer on kubernetes does not pick up IAM role via serviceAccount. #79

yogesh8177 opened this issue Jan 29, 2021 · 1 comment · May be fixed by #275

Comments

@yogesh8177
Copy link

yogesh8177 commented Jan 29, 2021

Deploying KCL consumer via kubernetes on aws EKS service does not pick up IAM role from serviceAccount with AWSCredentialsProvider = DefaultAWSCredentialsProviderChain, instead it uses node level role.

Following environment variables are present in the service, however it still doesn't seem to pick it up. However it works when I provide AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY.

AWS_DEFAULT_REGION=<region>
AWS_REGION=<region>
AWS_ROLE_ARN=<role-arn>
AWS_WEB_IDENTITY_TOKEN_FILE=<token-path>
@gmaghera
Copy link

gmaghera commented Mar 1, 2021

We are bumping into this too. https://aws.amazon.com/blogs/opensource/introducing-fine-grained-iam-roles-service-accounts/ is something we have asked our engineering teams to follow, but it seems to conflict with the lack of support here.

Is there maybe some setting that would result in the IAM role for service account getting seen by aws-kcl?

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

Successfully merging a pull request may close this issue.

2 participants