You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm trying to run the Kinesis Python client on EKS, where the credentialing mechanism is web identity token. However, when I set the credential provider to the default chain like so:
the workers seem to attempt to use the instance profile to access AWS APIs instead, based on the request logs.
I have confirmed that the IAM policies are set up correctly. When I manually set the access key credentials in the environment (via AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY), the workers work correctly.
I believe a couple of things need to happen in order to support web identity tokens:
The AWS Java SDK version used in multilang needs to be bumped from 1.11.477 to at least 1.11.704, based on the documentation.
The aws-java-sdk-sts module needs to be added as a dependency, based on the debug log:
[DEBUG] AWSCredentialsProviderChain - Unable to load credentials from WebIdentityTokenCredentialsProvider: To use assume role profiles the aws-java-sdk-sts module must be on the class path.
The text was updated successfully, but these errors were encountered:
I'm trying to run the Kinesis Python client on EKS, where the credentialing mechanism is web identity token. However, when I set the credential provider to the default chain like so:
the workers seem to attempt to use the instance profile to access AWS APIs instead, based on the request logs.
I have confirmed that the IAM policies are set up correctly. When I manually set the access key credentials in the environment (via
AWS_ACCESS_KEY_ID
andAWS_SECRET_ACCESS_KEY
), the workers work correctly.I believe a couple of things need to happen in order to support web identity tokens:
multilang
needs to be bumped from1.11.477
to at least1.11.704
, based on the documentation.aws-java-sdk-sts
module needs to be added as a dependency, based on the debug log:The text was updated successfully, but these errors were encountered: