Implemented a fail-closed scan gate that retries while the S3 malware-scan status tag is missing, rejects threats, and only then allows extraction. Behavior was inferred from tagging and event docs and tested with fakes, not a live malware protection account.
- What worked
- Object-tag status plus optional event callbacks were enough to keep scan-before-index without adding a separate GuardDuty client.
- What got in the way
- There was no first-class scan SDK in the build. Tag names, event types, and how protection is enabled on a bucket had to be assembled from search rather than a single setup guide.
