Support for EKS 'IAM for service accounts' not default [1.11.623, 1.11.653] #2136

thundergolfer · 2019-10-29T23:01:50Z

Description

Despite the documentation saying a minimum version of 1.11.623 should allow IAM Service Accounts to works, I'm running pods and seeing that that run with the IAM role of the node and not the role linked to the IAM ServiceAccount I am running as.

Another using describes the same problem with 1.11.653 here.

I have discovered a hack that fixes the issue:

    // NOTE: For some unknown reason if this call isn't made then the following code
    // uses the K8s node's role and not the IAM ServiceAccount role.
    // TODO(Jonathon): Remove when the above weirdness is fixed.
    val client = AWSSecurityTokenServiceClientBuilder.standard.build
    val request = new GetCallerIdentityRequest()
    val _ = client.getCallerIdentity(request)

That above identity request returns the correct role, and then subsequently doing something like this, AmazonSNSAsyncClientBuilder.defaultClient(), will get me a client authenticated to the IAM role associated with the service account.

The text was updated successfully, but these errors were encountered:

thundergolfer · 2019-10-30T01:05:33Z

Something like this works:

AmazonS3ClientBuilder
      .standard()
      .withCredentials(WebIdentityTokenCredentialsProvider.create)
      .build()

So it's just a problem that WebIdentityTokenCredentialsProvider isn't in the default toolchain.

zoewangg · 2019-11-07T22:03:45Z

Hi @thundergolfer
WebIdentityTokenCredentialsProvider is in the default credential provider chain in v1 though.

aws-sdk-java/aws-java-sdk-core/src/main/java/com/amazonaws/auth/DefaultAWSCredentialsProviderChain.java

Lines 45 to 50 in 5bafd0d

    
           public DefaultAWSCredentialsProviderChain() { 
        
               super(new EnvironmentVariableCredentialsProvider(), 
        
                     new SystemPropertiesCredentialsProvider(), 
        
                     new ProfileCredentialsProvider(), 
        
                     WebIdentityTokenCredentialsProvider.create(), 
        
                     new EC2ContainerCredentialsProviderWrapper());

Could it be possible that you had some other credentials providers available on your credential chain and took precedence?

thundergolfer · 2019-11-07T22:49:23Z

Hey @zoewangg thanks for the reply,

Yeh you're right seems it landed in the default chain in .620. I'm 95% sure I had no code that was configuring any providers. I was just requesting the default clients for SNS, S3 and leaving it up to the default chain.

Given that someone else has seen this is, I'm confident something is going on here.

Do you have any advice on how I would best track this down? Perhaps simply enabling DEBUG level logs would show behaviour of the provider chain?

zoewangg · 2019-11-07T22:57:06Z

Yeah, it'd be great if you could enable debug logging and provide the logs here (Be sure to redact any sensitive info from the logs)

anoopk19 · 2019-11-10T14:42:46Z

I am debugging a similar issue. AWS SDK fails to recognize AWS_WEB_IDENTITY_TOKEN_FILE environment variable and defaults to EC2ContainerCredentialsProviderWrapper.
SDK version used is : aws-sdk-java/1.11.671

Debug logs captured below,

2019-11-10T14:31:44,137 DEBUG [appenderator_merge_0] com.amazonaws.auth.AWSCredentialsProviderChain - Unable to load credentials from org.apache.druid.common.aws.ConfigDrivenAwsCredentialsConfigProvider@1de783b1: Unable to load AWS credentials from druid AWSCredentialsConfig
2019-11-10T14:31:44,138 DEBUG [appenderator_merge_0] com.amazonaws.auth.AWSCredentialsProviderChain - Unable to load credentials from org.apache.druid.common.aws.LazyFileSessionCredentialsProvider@6b9f21a6: cannot refresh AWS credentials
2019-11-10T14:31:44,138 DEBUG [appenderator_merge_0] com.amazonaws.auth.AWSCredentialsProviderChain - Unable to load credentials from EnvironmentVariableCredentialsProvider: Unable to load AWS credentials from environment variables (AWS_ACCESS_KEY_ID (or AWS_ACCESS_KEY) and AWS_SECRET_KEY (or AWS_SECRET_ACCESS_KEY))
2019-11-10T14:31:44,139 DEBUG [appenderator_merge_0] com.amazonaws.auth.AWSCredentialsProviderChain - Unable to load credentials from SystemPropertiesCredentialsProvider: Unable to load AWS credentials from Java system properties (aws.accessKeyId and aws.secretKey)
2019-11-10T14:31:44,139 DEBUG [appenderator_merge_0] com.amazonaws.auth.AWSCredentialsProviderChain - Unable to load credentials from com.amazonaws.auth.profile.ProfileCredentialsProvider@22343cb: profile file cannot be null
2019-11-10T14:31:44,150 DEBUG [appenderator_merge_0] com.amazonaws.auth.AWSCredentialsProviderChain - Loading credentials from com.amazonaws.auth.EC2ContainerCredentialsProviderWrapper@44e06fc8

thundergolfer · 2019-11-10T23:28:08Z

In those logs WebIdentity isn't present at all, and it seems you're on the latest version. It's skipping over it from ProfileCredentials to EC2ContainerCredentials...

What's that on the end here -> com.amazonaws.auth.EC2ContainerCredentialsProviderWrapper@44e06fc8. Is it a commit hash?

chriswilding · 2019-11-14T11:04:43Z

I think I'm experiencing the same issue or something similar. Yesterday I updated my application to use a service account and also updated the aws-java-sdk to v1.11.673. Adding my logs here in case they help.

The app fails to deploy to EKS and hits CrashLoopBackOff. In the logs I can't see WebIdentityTokenCredentialsProvider -

{"@timestamp":"2019-11-14T10:47:56.466+00:00","@version":"1","message":"Unable to load credentials from EnvironmentVariableCredentialsProvider: Unable to load AWS credentials from environment variables (AWS_ACCESS_KEY_ID (or AWS_ACCESS_KEY) and AWS_SECRET_KEY (or AWS_SECRET_ACCESS_KEY))","logger_name":"com.amazonaws.auth.AWSCredentialsProviderChain","thread_name":"main","level":"DEBUG","level_value":10000}
{"@timestamp":"2019-11-14T10:47:56.466+00:00","@version":"1","message":"Unable to load credentials from SystemPropertiesCredentialsProvider: Unable to load AWS credentials from Java system properties (aws.accessKeyId and aws.secretKey)","logger_name":"com.amazonaws.auth.AWSCredentialsProviderChain","thread_name":"main","level":"DEBUG","level_value":10000}
{"@timestamp":"2019-11-14T10:47:56.466+00:00","@version":"1","message":"Unable to load credentials from com.amazonaws.auth.profile.ProfileCredentialsProvider@4287d447: profile file cannot be null","logger_name":"com.amazonaws.auth.AWSCredentialsProviderChain","thread_name":"main","level":"DEBUG","level_value":10000}
{"@timestamp":"2019-11-14T10:47:56.472+00:00","@version":"1","message":"Unable to load configuration from com.amazonaws.monitoring.EnvironmentVariableCsmConfigurationProvider@54e7391d: Unable to load Client Side Monitoring configurations from environment variables!","logger_name":"com.amazonaws.monitoring.CsmConfigurationProviderChain","thread_name":"main","level":"DEBUG","level_value":10000}
{"@timestamp":"2019-11-14T10:47:56.472+00:00","@version":"1","message":"Unable to load configuration from com.amazonaws.monitoring.SystemPropertyCsmConfigurationProvider@50b8ae8d: Unable to load Client Side Monitoring configurations from system properties variables!","logger_name":"com.amazonaws.monitoring.CsmConfigurationProviderChain","thread_name":"main","level":"DEBUG","level_value":10000}
{"@timestamp":"2019-11-14T10:47:56.472+00:00","@version":"1","message":"Unable to load configuration from com.amazonaws.monitoring.ProfileCsmConfigurationProvider@3c8bdd5b: Unable to load config file","logger_name":"com.amazonaws.monitoring.CsmConfigurationProviderChain","thread_name":"main","level":"DEBUG","level_value":10000}
{"@timestamp":"2019-11-14T10:47:56.479+00:00","@version":"1","message":"Unable to load credentials from EnvironmentVariableCredentialsProvider: Unable to load AWS credentials from environment variables (AWS_ACCESS_KEY_ID (or AWS_ACCESS_KEY) and AWS_SECRET_KEY (or AWS_SECRET_ACCESS_KEY))","logger_name":"com.amazonaws.auth.AWSCredentialsProviderChain","thread_name":"main","level":"DEBUG","level_value":10000}
{"@timestamp":"2019-11-14T10:47:56.479+00:00","@version":"1","message":"Unable to load credentials from SystemPropertiesCredentialsProvider: Unable to load AWS credentials from Java system properties (aws.accessKeyId and aws.secretKey)","logger_name":"com.amazonaws.auth.AWSCredentialsProviderChain","thread_name":"main","level":"DEBUG","level_value":10000}
{"@timestamp":"2019-11-14T10:47:56.480+00:00","@version":"1","message":"Unable to load credentials from com.amazonaws.auth.profile.ProfileCredentialsProvider@4287d447: profile file cannot be null","logger_name":"com.amazonaws.auth.AWSCredentialsProviderChain","thread_name":"main","level":"DEBUG","level_value":10000}
{"@timestamp":"2019-11-14T10:47:56.480+00:00","@version":"1","message":"Unable to load credentials from EnvironmentVariableCredentialsProvider: Unable to load AWS credentials from environment variables (AWS_ACCESS_KEY_ID (or AWS_ACCESS_KEY) and AWS_SECRET_KEY (or AWS_SECRET_ACCESS_KEY))","logger_name":"com.amazonaws.auth.AWSCredentialsProviderChain","thread_name":"main","level":"DEBUG","level_value":10000}
{"@timestamp":"2019-11-14T10:47:56.480+00:00","@version":"1","message":"Unable to load credentials from SystemPropertiesCredentialsProvider: Unable to load AWS credentials from Java system properties (aws.accessKeyId and aws.secretKey)","logger_name":"com.amazonaws.auth.AWSCredentialsProviderChain","thread_name":"main","level":"DEBUG","level_value":10000}
{"@timestamp":"2019-11-14T10:47:56.480+00:00","@version":"1","message":"Unable to load credentials from com.amazonaws.auth.profile.ProfileCredentialsProvider@4287d447: profile file cannot be null","logger_name":"com.amazonaws.auth.AWSCredentialsProviderChain","thread_name":"main","level":"DEBUG","level_value":10000}
... this repeats many times

I also get a StackOverflowError with the stack trace after the AWSCredentialsProviderChain repeated many times. The stack trace does include reference the WebIdentityTokenCredentialsProvider -

Exception in thread "main" java.lang.StackOverflowError
	at java.io.UnixFileSystem.getBooleanAttributes0(Native Method)
	at java.io.UnixFileSystem.getBooleanAttributes(UnixFileSystem.java:242)
	at java.io.File.exists(File.java:819)
	at com.amazonaws.profile.path.cred.CredentialsDefaultLocationProvider.getLocation(CredentialsDefaultLocationProvider.java:33)
	at com.amazonaws.profile.path.AwsProfileFileLocationProviderChain.getLocation(AwsProfileFileLocationProviderChain.java:41)
	at com.amazonaws.auth.profile.ProfilesConfigFile.getCredentialProfilesFile(ProfilesConfigFile.java:200)
	at com.amazonaws.auth.profile.ProfilesConfigFile.<init>(ProfilesConfigFile.java:100)
	at com.amazonaws.auth.profile.ProfileCredentialsProvider.getCredentials(ProfileCredentialsProvider.java:135)
	at com.amazonaws.auth.AWSCredentialsProviderChain.getCredentials(AWSCredentialsProviderChain.java:117)
	at com.amazonaws.http.AmazonHttpClient$RequestExecutor.getCredentialsFromContext(AmazonHttpClient.java:1225)
	at com.amazonaws.http.AmazonHttpClient$RequestExecutor.runBeforeRequestHandlers(AmazonHttpClient.java:801)
	at com.amazonaws.http.AmazonHttpClient$RequestExecutor.doExecute(AmazonHttpClient.java:751)
	at com.amazonaws.http.AmazonHttpClient$RequestExecutor.executeWithTimer(AmazonHttpClient.java:744)
	at com.amazonaws.http.AmazonHttpClient$RequestExecutor.execute(AmazonHttpClient.java:726)
	at com.amazonaws.http.AmazonHttpClient$RequestExecutor.access$500(AmazonHttpClient.java:686)
	at com.amazonaws.http.AmazonHttpClient$RequestExecutionBuilderImpl.execute(AmazonHttpClient.java:668)
	at com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:532)
	at com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:512)
	at com.amazonaws.services.securitytoken.AWSSecurityTokenServiceClient.doInvoke(AWSSecurityTokenServiceClient.java:1368)
	at com.amazonaws.services.securitytoken.AWSSecurityTokenServiceClient.invoke(AWSSecurityTokenServiceClient.java:1335)
	at com.amazonaws.services.securitytoken.AWSSecurityTokenServiceClient.invoke(AWSSecurityTokenServiceClient.java:1324)
	at com.amazonaws.services.securitytoken.AWSSecurityTokenServiceClient.executeAssumeRole(AWSSecurityTokenServiceClient.java:491)
	at com.amazonaws.services.securitytoken.AWSSecurityTokenServiceClient.assumeRole(AWSSecurityTokenServiceClient.java:464)
	at com.amazonaws.auth.STSAssumeRoleSessionCredentialsProvider.newSession(STSAssumeRoleSessionCredentialsProvider.java:321)
	at com.amazonaws.auth.STSAssumeRoleSessionCredentialsProvider.access$000(STSAssumeRoleSessionCredentialsProvider.java:37)
	at com.amazonaws.auth.STSAssumeRoleSessionCredentialsProvider$1.call(STSAssumeRoleSessionCredentialsProvider.java:76)
	at com.amazonaws.auth.STSAssumeRoleSessionCredentialsProvider$1.call(STSAssumeRoleSessionCredentialsProvider.java:73)
	at com.amazonaws.auth.RefreshableTask.refreshValue(RefreshableTask.java:257)
	at com.amazonaws.auth.RefreshableTask.blockingRefresh(RefreshableTask.java:213)
	at com.amazonaws.auth.RefreshableTask.getValue(RefreshableTask.java:154)
	at com.amazonaws.auth.STSAssumeRoleSessionCredentialsProvider.getCredentials(STSAssumeRoleSessionCredentialsProvider.java:299)
	at com.amazonaws.auth.STSAssumeRoleSessionCredentialsProvider.getCredentials(STSAssumeRoleSessionCredentialsProvider.java:36)
	at com.amazonaws.auth.profile.internal.securitytoken.STSProfileCredentialsServiceProvider.getCredentials(STSProfileCredentialsServiceProvider.java:71)
	at com.amazonaws.auth.WebIdentityTokenCredentialsProvider.getCredentials(WebIdentityTokenCredentialsProvider.java:72)

ConstantineXVI · 2019-11-15T15:54:08Z

When we implemented IRSA for our Java apps, we found that as configured in the default chain instance profile creds outrank WebIdentity; whereas in the Ruby and Go SDKs WebIdentity took precedence. Since the kubelet auths with IAM there's no way to not have an instance profile, and we don't have the option of blocking the metadata API for pods until every last service in our cluster is using IRSA. Unless the Java SDK changes its precedence order to match the other SDKs we're going to need to provide our own chains in all of our Java apps, which is less than ideal.

chriswilding · 2019-11-26T19:24:10Z

I was experiencing a StackOverflowError becuase another library was pulling in an older version of aws-java-sdk-sts which used to initialise a default credentials provider internally, updating this resolved the StackOverflowError.

Once that issue was resolved, as mentioned above we had to provide a credential chain to give WebIdentityTokenCredentialsProvider precedence. It would be helpful if the java sdk's default credentials provider precedence order was changed to give the WebIdentityTokenCredentialsProvider higher precedence.

MrpPolo · 2019-12-03T15:47:15Z

I also encounter same issue and I upgraded my aws-java-sdk-sts lib version(1.11.623) to same as s3 lib version (1.11.623),it fixed.

thundergolfer · 2019-12-03T22:52:57Z

In our case all our SDK libraries are on 1.11.659, but the problem persists.

millems · 2020-01-09T01:26:46Z

aws/aws-sdk-java-v2#1583 will increase the priority of the web identity environment variables in 2.x (and a similar change will be coming out for 1.11.x) to be higher than the profile file properties, but this is the only issue we could reproduce on our end.

Please make sure you're using the latest SDK runtime/core as well as the latest client version.

kamac · 2020-01-09T17:46:34Z

We've fixed this by adding aws-java-sdk-sts library to our build. We're on 1.11.699. (apparently when it's missing, default provider chain skips using web identity)

zoewangg · 2020-01-15T19:35:20Z

The fix has been released as part of 1.11.704 and please try with the latest version.

https://github.com/aws/aws-sdk-java/blob/master/CHANGELOG.md#111704-2020-01-09

thundergolfer · 2020-01-15T23:41:27Z

We added 1.11.704 last week-ish, and it looks to have fixed the issue. 🎉

zoewangg · 2020-01-21T02:22:18Z

@thundergolfer Thanks for reporting back! Closing the issue. Feel free to reopen if you have further question.

bqnguyen94 · 2020-01-22T09:18:55Z

The fix has been released as part of 1.11.704 and please try with the latest version.

https://github.com/aws/aws-sdk-java/blob/master/CHANGELOG.md#111704-2020-01-09

We added 1.11.704 last week-ish, and it looks to have fixed the issue. 🎉

So to clarify, we need to upgrade SDKs to ^1.11.704 and also include aws-java-sdk-sts@^1.11.704? We found that without aws-java-sdk-sts pods will not use the web identity token credentials no matter what version of the SDK it is.

jhonatanmorais · 2020-01-23T17:36:20Z

The fix has been released as part of 1.11.704 and please try with the latest version.
https://github.com/aws/aws-sdk-java/blob/master/CHANGELOG.md#111704-2020-01-09

We added 1.11.704 last week-ish, and it looks to have fixed the issue. 🎉

So to clarify, we need to upgrade SDKs to ^1.11.704 and also include aws-java-sdk-sts@^1.11.704? We found that without aws-java-sdk-sts pods will not use the web identity token credentials no matter what version of the SDK it is.

I tried to upgrade aws-java-sdks to 1.11.704, also including aws-java-sdk-sts@1.11.704, without code changes, and it didn't work:

sqs = AmazonSQSClientBuilder.defaultClient()

Changing my client initialization to this, it works:

val awsCredentialProvider = WebIdentityTokenCredentialsProvider
            .builder()
            .roleArn(System.getenv("AWS_ROLE_ARN"))
            .roleSessionName(System.getenv("AWS_ROLE_SESSION_NAME"))
            .webIdentityTokenFile(System.getenv("AWS_WEB_IDENTITY_TOKEN_FILE"))
            .build()
        val sqs = AmazonSQSClientBuilder.standard().withCredentials(
            awsCredentialProvider
        ).build()

If AmazonSQSClientBuilder.defaultClient() returns DefaultAWSCredentialsProviderChain, and according to https://docs.aws.amazon.com/AWSJavaSDK/latest/javadoc/com/amazonaws/auth/DefaultAWSCredentialsProviderChain.html WebIdentityTokenCredentialsProvider is already included on DefaultAWSCredentialsProviderChain, with higher precedence,
should this be working already?

Detail: I'm also using IAM Policy attached on EC2 worker nodes (EKS cluster purposes).

debora-ito · 2020-01-23T19:58:06Z

@jhonatanmorais before investigating it further, can you make sure there's no conflicting versions in your environment? Could you run mvn dependency:tree and post the relevant output?

jhonatanmorais · 2020-01-23T20:20:37Z

@debora-ito:

+--- com.amazonaws:amazon-sqs-java-messaging-lib:1.0.8
|    \--- org.apache.geronimo.specs:geronimo-jms_1.1_spec:1.1.1
+--- com.amazonaws:aws-java-sdk-sqs:1.11.708
|    +--- com.amazonaws:aws-java-sdk-core:1.11.708
|    \--- com.amazonaws:jmespath-java:1.11.708
|         \--- com.fasterxml.jackson.core:jackson-databind:2.6.7.3 (*)
+--- com.amazonaws:aws-java-sdk-core:1.11.708 (*)
+--- com.amazonaws:aws-java-sdk-sts:1.11.708
|    +--- com.amazonaws:aws-java-sdk-core:1.11.708 (*)
|    \--- com.amazonaws:jmespath-java:1.11.708 (*)
+--- org.apache.logging.log4j:log4j-api:2.13.0
\--- org.apache.logging.log4j:log4j-core:2.13.0
     \--- org.apache.logging.log4j:log4j-api:2.13.0

bqnguyen94 · 2020-01-28T02:05:37Z

@jhonatanmorais so I assume you have tried WebIdentityTokenCredentialsProvider.create() and it did not work as well?

jhonatanmorais · 2020-01-28T17:25:43Z

@bqnguyen94 I've tried only those two scenarios mentioned above.

this is required to support EKS IAM roles for service accounts, see: aws/aws-sdk-java#2136 Co-authored-by: Valentino Gattuso <valentino.gattuso@shipyardtech.com>

aws/aws-sdk-java#2136

Despite since `software.amazon.awssdk:2.10.11`, the `WebIdentityTokenFileCredentialsProvider` is part of the default credentials chain, it will only be enabled if `software.amazon.awssdk:sts` is on the classpath, which is mentioned in the javadocs: "Use of this credentials provider requires the 'sts' module to be on the classpath". See aws/aws-sdk-java#2136

thundergolfer changed the title ~~Java SDK support for EKS 'IAM for service accounts' not working [1.11.623, 1.11.653]~~ Support for EKS 'IAM for service accounts' not default [1.11.623, 1.11.653] Oct 30, 2019

zoewangg added work-in-progress guidance Question that needs advice or information. and removed work-in-progress labels Nov 5, 2019

zoewangg added investigating This issue is being investigated and/or work is in progress to resolve the issue. and removed guidance Question that needs advice or information. labels Nov 11, 2019

lachlancooper mentioned this issue Jan 9, 2020

Update AWS SDK to 1.11.658 prometheus/cloudwatch_exporter#224

Merged

zoewangg closed this as completed Jan 21, 2020

vavvolo mentioned this issue Mar 13, 2020

bump aws sdk version to support EKS IAM roles for service accounts gkatzioura/CloudStorageMaven#77

Merged

FaHeymann mentioned this issue Mar 13, 2020

fix(s3): Update aws-sdk to v1.11.717 spinnaker/front50#740

Closed

JPLachance mentioned this issue Mar 17, 2020

Add the support for the WebIdentityTokenCredentialsProvider to run in AWS EKS logstash-plugins/logstash-input-kinesis#76

Closed

This was referenced Mar 20, 2020

Include STS so web identity works rundeck-plugins/rundeck-ec2-nodes-plugin#106

Merged

Include STS so web identity will work rundeck-plugins/aws-s3-model-source#7

Merged

Include STS so web identity works rundeck-plugins/rundeck-s3-log-plugin#36

Merged

jonathan-mothership mentioned this issue Mar 25, 2020

Fix/irsa prometheus/cloudwatch_exporter#263

Closed

jasonstitt mentioned this issue Jul 24, 2020

AWS SDK update needed to use Kubernetes ServiceAccount credentials jenkinsci/aws-credentials-plugin#78

Open

adamhooper added a commit to overview/overview-server that referenced this issue Aug 2, 2020

Add aws-sdk-java-sts, for container auth

3b40045

aws/aws-sdk-java#2136

mozai mentioned this issue Oct 29, 2020

cloudwatch taking worker role in AWS and not using OIDC prometheus/cloudwatch_exporter#303

Closed

alexandrud mentioned this issue Feb 9, 2021

IRSA Support jenkinsci/ec2-fleet-plugin#259

Closed

missedone mentioned this issue Jun 17, 2021

k8s:push failed with aws ecr credential helper for docker eclipse-jkube/jkube#702

Closed

msangoi mentioned this issue Oct 29, 2021

Missing WebIdentityTokenCredentialsProvider with AWS SDK 1.11.507 tpunder/fm-sbt-s3-resolver#61

Closed

kevinwallimann mentioned this issue Dec 6, 2021

Fix/eks irsa auth AbsaOSS/hyperdrive-trigger#543

Merged

ghost mentioned this issue Jan 13, 2022

Plugin uses instance role instead of pod role jenkinsci/aws-secrets-manager-credentials-provider-plugin#172

Closed

GuoqinZheng-at mentioned this issue May 5, 2022

Add aws-java-sdk-sts module awslabs/amazon-kinesis-client-nodejs#129

Closed

ashleybill mentioned this issue Jun 28, 2022

WebIdentityTokenCredentialsProvider in default chain not working jcustenborder/kafka-config-provider-aws#7

Closed

c3-cam-keenan mentioned this issue Jan 11, 2023

AWSSecurityTokenServiceClient.doInvoke goes into infinite loop #2760

Closed

groldan mentioned this issue May 31, 2023

Add dependency on aws sts to support IAM roles for service accounts geoserver/geoserver-cloud#334

Merged

groldan mentioned this issue May 31, 2023

Add dependency on aws sts to support IAM roles for service accounts geoserver/geoserver-cloud#335

Merged

harmeet-singh-discovery mentioned this issue Jul 23, 2023

fix: Add aws-sts dependency in java sdk so that S3 client acquires IRSA role feast-dev/feast#3696

Merged

msaffitz mentioned this issue Jul 29, 2023

Add aws sts library to support IRSA for logging airbytehq/airbyte-platform#263

Closed

2 tasks

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Support for EKS 'IAM for service accounts' not default [1.11.623, 1.11.653] #2136

Support for EKS 'IAM for service accounts' not default [1.11.623, 1.11.653] #2136

thundergolfer commented Oct 29, 2019

thundergolfer commented Oct 30, 2019

zoewangg commented Nov 7, 2019 •

edited

Loading

thundergolfer commented Nov 7, 2019

zoewangg commented Nov 7, 2019

anoopk19 commented Nov 10, 2019

thundergolfer commented Nov 10, 2019 •

edited

Loading

chriswilding commented Nov 14, 2019

ConstantineXVI commented Nov 15, 2019

chriswilding commented Nov 26, 2019

MrpPolo commented Dec 3, 2019 •

edited

Loading

thundergolfer commented Dec 3, 2019

millems commented Jan 9, 2020 •

edited

Loading

kamac commented Jan 9, 2020 •

edited

Loading

zoewangg commented Jan 15, 2020

thundergolfer commented Jan 15, 2020

zoewangg commented Jan 21, 2020

bqnguyen94 commented Jan 22, 2020

jhonatanmorais commented Jan 23, 2020 •

edited

Loading

debora-ito commented Jan 23, 2020

jhonatanmorais commented Jan 23, 2020

bqnguyen94 commented Jan 28, 2020

jhonatanmorais commented Jan 28, 2020

Support for EKS 'IAM for service accounts' not default [1.11.623, 1.11.653] #2136

Support for EKS 'IAM for service accounts' not default [1.11.623, 1.11.653] #2136

Comments

thundergolfer commented Oct 29, 2019

Description

thundergolfer commented Oct 30, 2019

zoewangg commented Nov 7, 2019 • edited Loading

thundergolfer commented Nov 7, 2019

zoewangg commented Nov 7, 2019

anoopk19 commented Nov 10, 2019

thundergolfer commented Nov 10, 2019 • edited Loading

chriswilding commented Nov 14, 2019

ConstantineXVI commented Nov 15, 2019

chriswilding commented Nov 26, 2019

MrpPolo commented Dec 3, 2019 • edited Loading

thundergolfer commented Dec 3, 2019

millems commented Jan 9, 2020 • edited Loading

kamac commented Jan 9, 2020 • edited Loading

zoewangg commented Jan 15, 2020

thundergolfer commented Jan 15, 2020

zoewangg commented Jan 21, 2020

bqnguyen94 commented Jan 22, 2020

jhonatanmorais commented Jan 23, 2020 • edited Loading

debora-ito commented Jan 23, 2020

jhonatanmorais commented Jan 23, 2020

bqnguyen94 commented Jan 28, 2020

jhonatanmorais commented Jan 28, 2020

zoewangg commented Nov 7, 2019 •

edited

Loading

thundergolfer commented Nov 10, 2019 •

edited

Loading

MrpPolo commented Dec 3, 2019 •

edited

Loading

millems commented Jan 9, 2020 •

edited

Loading

kamac commented Jan 9, 2020 •

edited

Loading

jhonatanmorais commented Jan 23, 2020 •

edited

Loading