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
Based on the solution provided in #307 I tried using Cosbench v0.4.3.0 to send AWS S3 v4 signature authorization, but I'm getting 400 responses back from an S3-compatible cloud storage service. The errors say "The V2 signature authorization mechanism you have provided is not supported. Please use AWS-HMAC-SHA256." In my Cosbench workload config file, I have the following as the storage type:
I've tried adding "-Dcom.amazonaws.services.s3.enableV4" to the java line in cosbench-start.sh, to no avail.
I thought v0.4.3.0 added support for AWS s3 v4 signature authorization. Does anyone know how to get Cosbench to send v4?
I'm running Cosbench on a Ubuntu 22.04 server. I've tried with JDK 11, 8, and 7. I have a proxy from mitmproxy.org running on the server so I can see the requests and responses in plaintext.
Thanks.
The text was updated successfully, but these errors were encountered:
Based on the solution provided in #307 I tried using Cosbench v0.4.3.0 to send AWS S3 v4 signature authorization, but I'm getting 400 responses back from an S3-compatible cloud storage service. The errors say "The V2 signature authorization mechanism you have provided is not supported. Please use AWS-HMAC-SHA256." In my Cosbench workload config file, I have the following as the storage type:
storage type="s3" config="path_style_access=true;accesskey=access-key;secretkey=secret-key;endpoint=https://s3-compatible-server;proxyhost=127.0.0.1;proxyport=8080;signer_version=V4"
I've tried adding "-Dcom.amazonaws.services.s3.enableV4" to the java line in cosbench-start.sh, to no avail.
I thought v0.4.3.0 added support for AWS s3 v4 signature authorization. Does anyone know how to get Cosbench to send v4?
I'm running Cosbench on a Ubuntu 22.04 server. I've tried with JDK 11, 8, and 7. I have a proxy from mitmproxy.org running on the server so I can see the requests and responses in plaintext.
Thanks.
The text was updated successfully, but these errors were encountered: