So the minio-sdk does not support the full object checksums as specified by the docs?
Generally you would provide the checksum of the whole object in the CompleteMultipartUpload request, along with the object size and the upload would be confirmed or failed from the S3 side - if I do this client-side and I compare it myself, it means I would now need to issue new requests to delete the object.

So the minio-sdk does not support the full object checksums as specified by the docs?

It does, but maybe not the way you want it to. PutObject is an abstraction. It will calculate a checksum if you ask it to. It does not allow you to set your own. You can use Core to do all requests manually.

I would now need to issue new requests to delete the object.

How often do you expect checksums to mismatch?

This is unfortunate for me. I am middleware and can't calculate the full checksum until all of the bytes have been sent. I can send the full file checksum (and part checksums if required) on CompleteMultipartUpload but I don't yet know the part checksums when the UploadPart headers are created.

I don't understand why this restriction is being enforced. AWS does not enforce it and it seems completely unnecessary.

@JustinKyleJames Parts can be uploaded with trailing headers.

@JustinKyleJames Parts can be uploaded with trailing headers.

Thanks and that was what I have been looking into. I don't think the library I am using supports trailing headers but I may be able to add support for it.