Support Uploads Get Immutable, Tenant-Scoped Object Keys to Prevent Overwrites

The article argues that support-platform attachments and their WebP or AVIF thumbnails should be stored under immutable, tenant-scoped object keys rather than reused filenames. Each key places the tenant ID first, then a stable attachment ID, an immutable upload version, and finally the representation, so tenants cannot collide and retries cannot replace a known-good original. The chosen version is published through database state rather than by overwriting an object. The author notes that object storage suits this private-media workflow but is not a substitute for storage-enforced protections such as WORM retention. A Go example uploads a derivative to a pre-created private bucket, validating key components, honoring rate-limit retry headers, and deriving an idempotency key from the key and content.