How does Wasabi handle multipart uploads?

Wasabi supports the AWS S3 API multipart upload capability that allows you to essentially 'chunk' a large file into separate parts that are automatically put back together as a single file when the file transmission is done.   The benefit of this approach is that a large file can be uploaded more efficiently and in the event of a file transmission failure, the storage app can resume uploading with the part that failed (vs. starting at the beginning).

This AWS document provides a good explanation of how multipart upload works in the S3 API.  Wasabi adheres to the approach described in this document with the following exception:

Wasabi does not currently support the AbortIncompleteMultipartUpload lifecycle action that allows you to configure a lifecycle policy that will delete aborted multiparts after a specified period of time.  Instead, Wasabi uses a fixed value of 30 days.  This means that after 30 days, any aborted multiparts are automatically deleted by Wasabi.  Wasabi plans to support the AbortIncompleteMultipartUpload lifecycle action in a future release.

Aborted multiparts occur when a multipart upload begins but is not completed due to a planned (the sending app intentionally stops the multipart upload) or unplanned (the transmission of the part is unexpectedly interrupted).   Wasabi, like AWS, bills for the storage associated with aborted multiparts as long as they are kept in the system as active storage or deleted storage that has not yet met the minimum storage retention period. 



Have more questions? Submit a request