How does Impossible Cloud handle aborted or non-completed multipart uploads (MPUs)?
This article explains how incomplete multipart uploads are managed in Impossible Cloud including retention, cleanup and billing.
Impossible Cloud supports S3 multipart upload (MPU) capabilities. This feature allows large files to be broken down into smaller parts that can be uploaded independently and reassembled automatically once all parts are successfully received. This mechanism is ideal for improving upload reliability, performance, and resilience for large data transfers.
What are aborted or non-completed MPUs?
There are two primary scenarios where MPUs may remain incomplete:
- Aborted MPUs: These occur when a multipart upload is intentionally stopped by the uploading application before all parts are uploaded or the upload is finalized. This may be part of normal application behavior (e.g., a user cancels an upload).
- Non-Completed MPUs: These happen when the multipart upload process is interrupted unintentionally—such as through network issues, client crashes, or other unforeseen disruptions—without being aborted or completed.
What happens with aborted or non-completed MPUs?
To prevent the accumulation of unused data and ensure optimal resource management, non-completed MPUs are automatically removed after 30 days from their initiation time.
Until then, incomplete MPUs to your storage utilization are included in your billing as long as they exist within the system.
To avoid unnecessary storage costs, customers are encouraged to explicitly abort MPUs that are no longer needed using the AbortMultipartUpload API call.