For a large file browser direct upload, use multipart upload with presigned parts, and make completion or abort an explicit application operation. That choice keeps retries bounded to one part instead of restarting a video or document, but it also means your service owns the upload state and cleanup path.
My production rule is simple: the browser never decides that an upload is complete. The server creates the session, records it, signs each part, verifies the returned part metadata, and completes only after every expected part has succeeded. A canceled session gets an abort request, even if the user has already closed the tab.
Short version: completion and abort belong to your application.
How should a large file browser direct upload use multipart parts?
The workflow has four stages. First, a trusted server creates a multipart session for the target bucket and object key. It returns an upload ID and a part plan.…