-
Notifications
You must be signed in to change notification settings - Fork 240
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Signature Version 4 for Request Authentication support for S3 #307
Comments
If this helps here is the configuration used for testing
|
hi,Did that solve? |
Hi, any Solution? |
I was able to get COSBench working with sigv4 by downloading the version from Hitachi. https://github.com/HitachiDataSystems/cosbench/releases/ More info on their site here: https://community.hitachivantara.com/s/article/hcp-storage-adaptor-for-cosbench I'm running on Amazon Linux (not Amazon Linux 2) and got up and running from a clean install with a single host using the commands below:
|
When running test to perform benchmarks against Amazon S3 or Minio (minio.io), I get this exception.
com.intel.cosbench.api.storage.StorageException: AmazonS3Exception: Status Code: 400, AWS Service: Amazon S3, AWS Request ID: 3L137, AWS Error Code: InvalidRequest, AWS Error Message: The authorization mechanism you have provided is not supported. Please use AWS4-HMAC-SHA256., S3 Extended Request ID: 3L137
It seems cosbench needs to use V4 version signature as mentioned in https://docs.aws.amazon.com/AmazonS3/latest/dev/UsingAWSSDK.html#specify-signature-version. I tested by adding the value as
-Dcom.amazonaws.services.s3.enableV4
in cosbench-start.sh but it still does not work. Any idea to fix this ?
The text was updated successfully, but these errors were encountered: