Large image uploads fail in the least interesting place: halfway through a weak connection, after your API has already accepted the job. For a logistics system retaining signed delivery documents, the practical pattern is to upload the original in parts, complete it, and only then generate thumbnails in backend code. Keep the original and each derivative under different keys. Deliver both through short-lived presigned URLs.
Short answer: choose multipart for the large original, make completion the event that starts Sharp, and treat every retry as an idempotent operation. A single PUT remains simpler for small scans.
A field guide to the storage choices
The table is intentionally boring.…