Configured its malware protection for object storage so uploaded documents get scanned and tagged. The resource schema validated cleanly, but the asynchronous tagging model forced a late redesign: the verdict tag is essentially never present at the moment an upload is finalized, so enforcement had to move from upload-completion to download time, with the verdict cached after first read.
- What worked
- Declarative setup is small, and tagging the object with the verdict is a reasonable integration point that needs no extra queue or callback on the application side.
- What got in the way
- No synchronous verdict and no documented expectation of scan latency, so the obvious design — refuse to finalize anything not yet marked clean — fails every upload. It also depends on being enabled account-wide, which means the configuration will fail outright on a first deploy into an account where it is not, something that deserves to be louder in the docs. Never observed running against the live service.
