wireapp/wire-server

Cargohold does not support AWS4-HMAC-SHA256 authorization mechanism for AWS

kvaps opened this issue · 1 comments

kvaps commented

Describe the bug
Hi, when I deploy wire-server on AWS eu-central-1 region I see the following error:

The authorization mechanism you have provided is not supported. Please use AWS4-HMAC-SHA256.

To Reproduce
Deploy cargohold on aws with next values:

cargohold:
  replicaCount: 3
  config:
    aws:
      region: "eu-central-1"
      s3Bucket: cargohold-s3-bucket
      s3Endpoint: https://s3.eu-central-1.amazonaws.com

Expected behavior
S3 is working

Full log

1:I,25:Listening on 0.0.0.0:8080,
1:E,7:request,1:=,32:9682a9e0e2f22dbcd77e555074b30014,497:S3Error {s3StatusCode = Status {statusCode = 400, statusMessage = "Bad Request"}, s3ErrorCode = "InvalidRequest", s3ErrorMessage = "The authorization mechanism you have provided is not supported. Please use AWS4-HMAC-SHA256.", s3ErrorResource = Nothing, s3ErrorHostId = Just "ELdlnrJNzsEmSFWgz2BCO6EGSAlmlXDsX5gDqyX8+hjadVE9tXY7DlfjDNKw7xhOniEwRm7yV2U=", s3ErrorAccessKeyId = Nothing, s3ErrorStringToSign = Nothing, s3ErrorBucket = Nothing, s3ErrorEndpointRaw = Nothing, s3ErrorEndpoint = Nothing},
1:E,7:request,1:=,32:9682a9e0e2f22dbcd77e555074b30014,378:Error {code = Status {statusCode = 500, statusMessage = "Internal Server Error"}, label = "server-error", message = "\US\65533\b\NUL\NUL\NUL\NUL\NUL\EOT\ETX\65533VJ\65533OIU\65533\&250\65533Q\65533M-.NL\a\65533\65533\65533S\65533\65533R\65533\DC4\\\65533\65533\65533\65533\65533\65533t\65533r\DC2\65533Rs\65533\65533\65533`q\65533T\65533\65533R-\NULv,\65533\65533=\NUL\NUL\NUL"},

Additional context
I installed wire-server on AWS using standard helm chart, with scylla, elasticsearchand and redis operators for the databases.
Cargohold image: quay.io/wire/cargohold:2.83.0

kvaps commented

Probably duplicated #876