S3 BLOB Creating failed. Nexus 3.88

Sonatype Nexus Repository
1

Hello! I am trying to create an S3 BLOB store for an S3-compatible bucket.

I am getting the following error:

An error occurred saving data. ValidationErrorXO{id=‘*’, message=‘The provided ‘x-amz-content-sha256’ header does not match what was computed. (Service: S3, Status Code: 400, Request ID: 0000019BE22293B594EA2EA8B6F7A728, Extended Request ID: 36AAAQAAEAABAAAQAAEAABAAAQAAEAABAAAaI=AAAAAAAAAAAAAAAAAAAAAAAAAA) (SDK Attempt Count: 1)’}

I tried setting the following parameters:
nexus.blobstore.s3.chunkedEncodingDisabled=true nexus.blobstore.s3.payloadSigningEnabled=false

It didn’t help. What other parameters can I add?

I can successfully connect to the bucket using rclone:

  • SigV4 (AWS4-HMAC-SHA256) is used, and the signature passed validation (no authentication errors)
  • The X-Amz-Content-Sha256 header is present
2

When we create temporary blobs (i.e. something not attached to an asset in Nexus) we include custom metadata, some “s3 compatible” systems do not correctly compute the signature for these requests.

3

What configuration changes can I make on the Nexus Repository side?
Which property or setting should I apply (e.g. in nexus.properties)?
Does Nexus offer any compatibility mode, relaxed signature verification, simplified request signing behavior, or other options to make it more tolerant to S3-compatible storage quirks (particularly regarding x-amz-content-sha256 handling)?

4

It isn’t Nexus verifying these requests, that is an error your storage is providing to Nexus that we surface.