Short answer: use a presigned browser upload for small avatars only when the application controls the object key, the storage policy isolates tenants, and the deployed origin passes a real CORS test; otherwise, proxy the bytes through the application and accept the bandwidth cost.
The easiest setup is rarely the one with the fewest lines of React. In an e-commerce system, an avatar is a small file attached to a customer or staff identity, and the dangerous part is not moving those bytes. It is proving that a tenant cannot guess, overwrite, or retrieve another tenant's object while deployments, retries, and stale browser tabs are doing their normal work.
What should a React or Next.js team verify before choosing private avatar object storage?
Start with the boundary. The browser should never choose a tenant prefix, authorize a bucket, or decide which account owns an object.…