Could you use the Apache jclouds STS supplier for consistency:

https://stackoverflow.com/questions/23520216/using-aws-s3-via-jclouds-how-to-assume-role

hey, i am still testing this change, btw, the sts api only supports assume role not assume role with web identity 🤔

Could you expand on your comment? Do you mean that the AWS STS library only supports assume role? Or do you mean the jclouds code only allows it? If the former, it would be better to remove the aws-java-sdk-sts dependency. But if the latter, I am willing to take this if you can explain more clearly what this means.

sure

assume role is:

• you have your own credentials (access key id and access secret key), then you have the role arn that you want to assume
• assume role with web identity is, you have only one role arn and one web identity token

jclouds doesn't have a way to let you load you default aws credentials including web identity token

and this is something like what we have done for azure

btw, default aws credential provider chan here could help the program to load default credentials from many kind of aws sdk compatible env like

• aws credentials: AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY
• iam role service account: AWS_ROLE_ARN, AWS_WEB_IDENTITY_TOKEN_FILE
• etc ...

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

What does this do?

without this, aws sdk will not be able to work with this error due to this exclude

    <dependency>
      <groupId>com.amazonaws</groupId>
      <artifactId>aws-java-sdk-s3</artifactId>
      <version>1.12.261</version>
      <scope>test</scope>
      <exclusions>
        <exclusion>
          <groupId>commons-logging</groupId>
          <artifactId>commons-logging</artifactId>
        </exclusion>
      </exclusions>
    </dependency>

I don't remember the full context for this from 8 years ago but e569b19 suggests that I configured the AWS SDK to use the sl4fj logging like the rest of S3Proxy/jclouds. Can you investigate this further?

i tried to remove that dependency and i got this error

Caused by: java.lang.NoClassDefFoundError: Could not initialize class com.amazonaws.auth.DefaultAWSCredentialsProviderChain
	at org.gaul.s3proxy.Main$2.get(Main.java:399)
	at org.gaul.s3proxy.Main$2.get(Main.java:396)
	at org.jclouds.rest.internal.RestAnnotationProcessor.apply(RestAnnotationProcessor.java:241)
	at org.jclouds.rest.internal.RestAnnotationProcessor.apply(RestAnnotationProcessor.java:137)
	at org.jclouds.rest.internal.InvokeHttpMethod.toCommand(InvokeHttpMethod.java:189)
	at org.jclouds.rest.internal.InvokeHttpMethod.invoke(InvokeHttpMethod.java:85)
	at org.jclouds.rest.internal.InvokeHttpMethod.apply(InvokeHttpMethod.java:74)
	at org.jclouds.rest.internal.InvokeHttpMethod.apply(InvokeHttpMethod.java:45)
	at org.jclouds.rest.internal.DelegatesToInvocationFunction.handle(DelegatesToInvocationFunction.java:156)
	at org.jclouds.rest.internal.DelegatesToInvocationFunction.invoke(DelegatesToInvocationFunction.java:123)
	at jdk.proxy2/jdk.proxy2.$Proxy65.getBucketLocation(Unknown Source)
	at org.jclouds.s3.config.S3HttpApiModule$3.load(S3HttpApiModule.java:129)
	at org.jclouds.s3.config.S3HttpApiModule$3.load(S3HttpApiModule.java:125)
	at com.google.common.cache.LocalCache$LoadingValueReference.loadFuture(LocalCache.java:3574)
	at com.google.common.cache.LocalCache$Segment.loadSync(LocalCache.java:2316)
	at com.google.common.cache.LocalCache$Segment.lockedGetOrLoad(LocalCache.java:2189)
	at com.google.common.cache.LocalCache$Segment.get(LocalCache.java:2079)

i figured out that the program could only work when this dependency is added 😢

any hints? 🤔 as i am not familiar with java really 😢

i saw these imports

import org.apache.commons.logging.Log;
import org.apache.commons.logging.LogFactory;

in the class definition

public class DefaultAWSCredentialsProviderChain extends AWSCredentialsProviderChain {
...
}

public class AWSCredentialsProviderChain implements AWSCredentialsProvider {
....
}

I don't know if it is possible to replace the logging that the package has imported 🤔

Could you remove the <scope>test</scope> from <artifactId>jcl-over-slf4j</artifactId>? This should address the error.

@gaul yep, that works!, thanks! i removed the common logging dependency

Could you expand on your comment? Do you mean that the AWS STS library only supports assume role? Or do you mean the jclouds code only allows it? If the former, it would be better to remove the aws-java-sdk-sts dependency. But if the latter, I am willing to take this if you can explain more clearly what this means.