How to use s3-proxy with AWS named profiles

[oxyno-zeta]

How to use s3-proxy with AWS named profiles

[gites]

I was able to configure s3-proxy to use named profiles. The secret souce was setting AWS_SDK_LOAD_CONFIG (https://docs.aws.amazon.com/sdk-for-go/api/aws/session/)
The final config looks like this:

          - name: AWS_SDK_LOAD_CONFIG
            value: "true"
          - name: AWS_PROFILE
            value: some-profile-name

[oxyno-zeta]

Hello !

Thanks for your issue.
I'm afraid that this isn't possible in the application for the moment. I think without any environment variables declared, the AWS client will fallback to file and use the default profile but this isn't managed by s3-proxy itself.
The config is asking 2 files containing the 2 secrets or environment variables or a combination of the 2 to configure the AWS credentials.

Regards,

Oxyno-zeta

[gites]

I tried to use default profile but it is also failing.
I set:

        - name: AWS_SHARED_CREDENTIALS_FILE
          value: /home/proxy/.aws/credentials
        - name: AWS_PROFILE
          value: default

but still getting the same error message:

"NoCredentialProviders: no valid providers in chain. Deprecated.\n\tFor verbose messaging see aws.Config.CredentialsChainVerboseErrors"

[oxyno-zeta]

I was afraid of this. I'm sorry but you will have to change to environment variables or files containing plain secrets.
Or you can contribute and create the support for that.

Regards,

Oxyno-zeta

[oxyno-zeta]

Awesome ! That's a great thing. Thanks for this share.