x-amz-checksum-algorithm for multipart uploads #347
Labels
No Label
AdminAPI
Bug
Check AWS
CI
Correctness
Critical
Documentation
Ideas
Improvement
Low priority
Newcomer
Performance
S3 Compatibility
Testing
Usability
No Milestone
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: Deuxfleurs/garage#347
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
amazon supports setting a
x-amz-checksum-algorithm
header in the initial multipart upload: https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateMultipartUpload.html#API_CreateMultipartUpload_ResponseSyntaxthis can later than be used to validate the checksum of the completed object:
https://docs.aws.amazon.com/AmazonS3/latest/API/API_CompleteMultipartUpload.html#API_CompleteMultipartUpload_RequestSyntax
this would be great to add to garage since it would simplify multipart upload validation, for users. on the aws side it will actually fail if the checksum does not match.
(btw. minio does not have this feature yet and it is relativly new)
Thanks for your suggestion, I added some tags to your issue to track it.
We are currently working on Garage performances so we don't plan to work on it soon, but at the same time, it might be an interesting first contribution for newcomers :-)
Also, please note that Garage Multipart Implementation has some limitations compared to AWS one described in #204, so if you heavily rely on this feature, you should be aware of this.