It may happen that a MultiPart Upload with AWS S3 is started but not completed. In some cases, you can resume the upload from the latest updated chunk (e.g., contribution step), but sometimes is not possible (e.g., setup or finalize).
As a result, we should catch these situations and perform an abort of the upload in order to avoid unnecessary consumption of space inside AWS S3 with deattached pending requests.
It may happen that a MultiPart Upload with AWS S3 is started but not completed. In some cases, you can resume the upload from the latest updated chunk (e.g., contribution step), but sometimes is not possible (e.g., setup or finalize).
As a result, we should catch these situations and perform an
abortof the upload in order to avoid unnecessary consumption of space inside AWS S3 with deattached pending requests.