Upload fails with `The Content-MD5 you specified is not valid.`

[ctron]

Environment info

• NooBaa Version: 5.18.6
• Platform: minikube v1.36.0

Actual behavior

Caused by:
    0: unhandled error (InvalidDigest)
    1: Error { code: "InvalidDigest", message: "The Content-MD5 you specified is not valid.", aws_request_id: "mcvs7oau-7yw3js-14t8", s3_extended_request_id: "mcvs7oau-7yw3js-14t8" }

Expected behavior

Should work

Steps to reproduce

Use the Rust SDK to upload a file:

    let body = FsBuilder::new().file(file).build().await?; // fails
    client
        .put_object()
        .bucket(BUCKET)
        .key("key")
        .body(body)
        .send()
        .await?;

More information - Screenshots / Logs / Other output

It just works with an actual AWS S3 bucket.

[ismaelpuerto]

also fails when executed via AWS CLI.

Edit:
We found a workaround, disable automatic checksum calculation by setting the following environment variables:

export AWS_REQUEST_CHECKSUM_CALCULATION=WHEN_REQUIRED
export AWS_RESPONSE_CHECKSUM_CALCULATION=WHEN_REQUIRED

Or configuration in the AWS config file (~/.aws/config):

[default]
request_checksum_calculation = when_required
response_checksum_calculation = when_required

@ctron in Rust, equivalent options are available to handle this scenario:

https://github.com/awslabs/aws-sdk-rust/blob/release-2025-07-09/sdk/aws-types/src/sdk_config.rs#L142-L143

[ctron]

I appreciate the workaround. However, I think "it should just work".

[liranmauda]

@ctron @ismaelpuerto

Are we sure that 5.18.6 is being used?
Could you test it using master?

[ctron]

How could I install master?

[liranmauda]

When installing, you can use the noobaa-core image noobaa/noobaa-core-<date>
Use the previous date.
For example, the latest for today is master-20250714
The same goes for the operator.