Hi again, So I am getting this error when I am trying to create a new repository.

│ {"error":"NoCredentialProviders: no valid providers in chain. Deprecated.\n\tFor verbose messaging see aws.Config.CredentialsChainVerboseErrors","file":"build/pkg/block/s3/ad │
│ apter.go:204","func":"pkg/block/s3.(*Adapter).streamToS3","host":"lakefs.xxxx.xxxxxxxx","level":"error","method":"POST","msg":"failed to sign request","operation":"Put │
│ Object","path":"/api/v1/repositories","request_id":"280774a6-702f-416f-ab81-b89101b57309","service_name":"rest_api","time":"2022-04-22T07:58:34Z"}

I understand it is a similar issue to this one (ref: https://github.com/treeverse/lakeFS/issues/1728 ). But I am using s3 directly and my

configmap

looks like this:

blockstore:
      type: s3
      s3:
        region: eu-west-1

the credentials are directly being exported as env var to lakefs as

LAKEFS_BLOCKSTORE_CREDENTIALS_ACCESS_KEY_ID

and

LAKEFS_BLOCKSTORE_CREDENTIALS_SECRET_ACCESS_KEY

Any pointers on which direction I should be looking at or any means to get more explicit logs would be helpful. Already tried: • Making sure this deployment has permissions from istio to reach s3 • Making sure that the envvars are available to the deployment pods and have correct values • Tried setting explicit s3 endpoint in the configmap i.e

<http://bucketname.s3.amazon.com|bucketname.s3.amazon.com>

Note: This is deployed behind istio but as mentioned earlier I am sure istio is allowing access to s3.