Implemented malware gating via S3 object tags from Malware Protection rather than a GuardDuty SDK, waiting for a clean tag before indexing and quarantining infected objects. No live scan was run.
- What worked
- A tag-based pending/clean/threat model fit the existing scan-then-index ports without copying objects across regions.
- What got in the way
- There was no first-class client in the dependency set, so behavior had to be inferred from object tags and pending errors instead of a dedicated scan API.
