InvalidPart: One or more of the specified parts could not be found. The part may not have been uploaded, or the specified entity tag may not match the part's entity tag.

[kasir-barati]

I have a very crud and simple script in TS and yet I am getting this weird looking error. Does not matter what I do it persists and does not allow me to complete the multipart upload.

Please help me to understand what I am doing wrong here?

I am following the docs, right? Or am I doing something wrong here?

You can see what I am doing here in this repo:

https://github.com/kasir-barati/bugs/tree/aws-s3-multipart-completion-error

[kasir-barati]

BTW I also tried to keep the double quotes around etags but nothing changed. I still get the same error 🥶 🥶

[kasir-barati]

I thought you cannot use SHA256 but it seems it is not the case:

SHA-256 (SHA256): Supports both full object and composite algorithm types.

— Ref.

[kasir-barati]

Update

For full object checksums, you can use CRC-64/NVME (CRC64NVME), CRC-32 (CRC32), or CRC-32C (CRC32C) checksum algorithms in S3. Full object checksums in multipart uploads are only available for CRC-based checksums because they can linearize into a full object checksum. This linearization allows Amazon S3 to parallelize your requests for improved performance. In particular, S3 can compute the checksum of the whole object from the part-level checksums. This type of validation isn’t available for other algorithms, such as SHA and MD5. Because S3 has default integrity protections, if objects are uploaded without a checksum, S3 automatically attaches the recommended full object CRC-64/NVME (CRC64NVME) checksum algorithm to the object.

TLDR

• AWS S3 does not support SHA256 for full object checksums.

[kasir-barati]

Stackoverflow Q&A

BTW I have formulated my question in this stackoverflow Q&A, so if you know what is the problem I would love to learn from you: https://stackoverflow.com/questions/79440191/invalid-checksum-when-using-multipart-upload-with-full-object-checksum-in-nodejs

[kasir-barati]

I guess either I've found a bug in this lib or my code 😁, it seems like it does not matter if I say COMPOSITE or FULL_OBJECT. AWS will return the same checksum hash for my object. Look at this commit to understand what I mean.

You can follow the instructions here to see it for yourself, try to change that value to FULL_OBJECT or COMPOSITE. It does not change the returned checksum from S3.

[kasir-barati]

BTW here is my question on AWS forum: https://repost.aws/questions/QU5H7iryj4S3q4u5-UCsmasQ/xamzcontentchecksummismatch-the-provided-x-amz-checksum-header-does-not-match-what-was-computed

[kasir-barati]

New Findings

So it seems there is a serious problem in AWS S3's API and with the current API we cannot actually pass the checksum of the entire object to the AWS. Currently I am looking around to see if I can get this to works somehow since this is very important in my case.

#6742 (comment)