Replies: 3 comments
-
C:\Users\Administrator>aws s3api --endpoint http://192.168.95.200:9878 create-bucket --bucket=wordcount |
Beta Was this translation helpful? Give feedback.
-
http://192.168.95.200:9878/bucketname InvalidRequest
Error creating s3 auth info. The request may not be signed using AWS V4 signing algorithm, or might be invalid
|
Beta Was this translation helpful? Give feedback.
-
Are you referring to setting the access ID and secret key for the client? Since you are using an S3 client, there is nothing from Ozone running on the client side so all client configuration would be done for the S3 client according to the S3 docs Have you tried doing as the CLI suggested? Check out the Ozone S3 docs under the "Security" section for what values to use for access ID and secret key. Note:
However, I think you still need to set them to something in this case, otherwise the AWS client will fail as you have seen. |
Beta Was this translation helpful? Give feedback.
-
The URL of S3 can be opened. See the picture. Why can't I test it with awscli? Ozone has not configured S3 authentication.
s3的url可以打开,见图,为什么我用awscli测试不通呢,ozone没有配置s3认证,debug :
Beta Was this translation helpful? Give feedback.
All reactions