In some of AWS’s newer tools for container credentials, the token is provided via a file whose path is specified by AWS_CONTAINER_AUTHORIZATION_TOKEN_FILE, rather than being set directly with AWS_CONTAINER_AUTHORIZATION_TOKEN. Is it possible to update the container credential provider to support this?
This will allow support for EKS Pod Identity, which is the AWS recommended approach for using IAM roles with pods.
In some of AWS’s newer tools for container credentials, the token is provided via a file whose path is specified by AWS_CONTAINER_AUTHORIZATION_TOKEN_FILE, rather than being set directly with AWS_CONTAINER_AUTHORIZATION_TOKEN. Is it possible to update the container credential provider to support this?
This will allow support for EKS Pod Identity, which is the AWS recommended approach for using IAM roles with pods.