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
Please let me know, what is going wrong here, Should the "host name" be matched? Does the signature creation depend on the hostname? I was blocked with this, how can we fix the problem, any suggestion would be helpful.
The text was updated successfully, but these errors were encountered:
Hello Team,
We are running the s3proxy on 8080 post with following S3PROXY_CONFIGURATION:
JCLOUDS_CREDENTIAL : <AWS_SECRET_KEY>
JCLOUDS_ENDPOINT : https://s3.amazonaws.com
JCLOUDS_IDENTITY :<AWS_ACCESS_KEY_ID>
JCLOUDS_REGIONS : eu-west-1
JCLOUD_PROVIDER : aws-s3
LOG_LEVEL : debug
S3PROXY_AUTHORIZATION : aws-v2-or-v4
S3PROXY_CREDENTIAL : <S3_PROXY_SECRET_KEY>
S3PROXY_IDENTITY : <S3_PROXY_ACCESS_KEY_ID>
Our s3proxy is behind the istio-gateway, and exposed public endpoint as follows "https://mydomain.com/s3proxy"
And the istio will redirect its inbound request to "HTTP://localhost:8080"
When we use the S3client with overridden endpoint as follows
I'm seeing the following error
Please let me know, what is going wrong here, Should the "host name" be matched? Does the signature creation depend on the hostname? I was blocked with this, how can we fix the problem, any suggestion would be helpful.
The text was updated successfully, but these errors were encountered: