Short answer: use a presigned single-object upload for ordinary classroom images, then add multipart only when an image is large enough that retrying the whole object is operationally painful. The retention policy should decide what metadata and temporary parts survive, not the upload API.
For an edtech platform, the useful unit is a tenant-scoped export of product images: course thumbnails, workbook covers, and lesson illustrations. The browser uploads directly to object storage; an application service authorizes the object key and later produces an export containing only that tenant's retained objects. This keeps application servers out of the image byte path, but it makes deletion, expiry, and incomplete uploads part of the design.
What is the bill actually made of?
The visible object size is only one term. The harder-to-see terms are duplicate uploads after a timeout, abandoned multipart parts, export staging objects, and retained metadata that still points at deleted images.…