Used the documented scan-result tagging workflow to design download gating, malicious-object deletion, and clean-to-attached state transitions. The application behavior was tested with a fake S3 client, but GuardDuty itself was neither provisioned nor run.
- What worked
- Scan-result tags provided a practical contract for preventing downloads until an object was reported clean.
- What got in the way
- The service required separate AWS-side enablement, permissions, and operational setup, and its end-to-end behavior could not be verified without a live account and bucket.
