Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Support authentication with AWS_WEB_IDENTITY_TOKEN_FILE

See original GitHub issue

Use IAM Service Account roles results in the environment variables AWS_ROLE_ARN and AWS_WEB_IDENTITY_TOKEN_FILE which should be usable for auth.

https://docs.aws.amazon.com/eks/latest/userguide/iam-roles-for-service-accounts-technical-overview.html#pod-configuration

https://docs.aws.amazon.com/eks/latest/userguide/iam-roles-for-service-accounts-minimum-sdk.html

This project appears to be using a new enough SDK, so probably something wrong with the way it is initialised?

Issue Analytics

State:
Created 3 years ago
Comments:7 (3 by maintainers)

Top GitHub Comments

1reaction

brian-brazilcommented, Aug 14, 2020

Great, so not an issue on our end.

1reaction

james-callahancommented, Aug 13, 2020

We don’t support taking configuration from the environment - only the config file, so anything like this is up the the AWS library.

I believe the issue is in the way that the AWS library is being initialised.

e.g. use DefaultAWSCredentialsProviderChain

Top Results From Across the Web

AssumeRoleWithWebIdentity - AWS Security Token Service

Returns a set of temporary security credentials for users who have been authenticated in a mobile or web application with a web identity ......

Add support for AWS Web Identity Token File auth #119 - GitHub

I've deployed a delta-sharing server to an AWS Kubernetes cluster (EKS) which uses ... Add support for AWS Web Identity Token File auth...

StsWebIdentityTokenFileCredent...

An implementation of AwsCredentialsProvider that periodically sends an AssumeRoleWithWebIdentityRequest to the AWS Security Token Service to maintain ...

Authentication and Credentials - ACK - GitHub Pages

There are multiple ways in which you can configure an ACK service controller to use a particular set of AWS credentials: Web identity...

Unable to load AWS credentials from any provider in the chain ...

The containers in your pods must use an AWS SDK version that supports assuming an IAM role via an OIDC web identity token...