Support Media Uploads Go Direct to Object Storage Using Signed Multipart Transfers
The article recommends storing customer-support recordings and screenshots in private object storage and uploading them directly via short-lived signed URLs rather than routing bytes through the application server. It advises using multipart uploads for large files so a failed part only retries its own segment, with bounded parallelism for throughput. Originals and thumbnails should use separate immutable keys, since the storage lacks versioning and conditional writes, and lifecycle rules can clean up temporary derivatives. The author notes limits: lifecycle expiry operates only in one-day increments, and abandoned multipart fragments need separate handling. The backend authenticates the agent, issues signed part URLs, and completes the upload, while the browser sends the data without the application's credentials.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.


Discussion (0)
Log in to join the discussion and vote.
Log in