Fintech Training Artifact Uploads: Using Signed URLs and Upload Receipts for Private Storage
An on-call engineer facing a missing artifact receipt should halt promotion of the affected training run rather than retry an opaque upload. The article recommends that private fintech artifacts use a backend-generated presigned URL, with bytes uploaded directly from the browser and a separate receipt recorded before the run is marked complete. It compares Supabase Storage, Amazon S3, Cloudflare R2, and Google Cloud Storage, noting which suits frontend-led teams versus platform teams that need full storage controls. It stresses that the storage provider only accepts bytes and serves signed access, while the application must still handle authorization, tenant-to-key mapping, retention, and state transitions. The piece also presents Infrai as an option for consolidating storage and backend services under one key and bill, with CORS handled outside the frontend workflow.
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