You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I’m using Serverless ClamScan to scan files in a bucket that stores user data. In some cases, my server generates and stores files in a user’s folder. These files need to be available to the user immediately, and since they originate from my server, I don’t need them to be scanned.
Is there a way to configure Serverless ClamScan to ignore these files?
I considered adding a "CLEAN" tag when uploading the file to make it available instantly. However, will the file still be scanned in this case? Is there a better approach to bypass scanning for trusted files?
The text was updated successfully, but these errors were encountered:
I’m using Serverless ClamScan to scan files in a bucket that stores user data. In some cases, my server generates and stores files in a user’s folder. These files need to be available to the user immediately, and since they originate from my server, I don’t need them to be scanned.
Is there a way to configure Serverless ClamScan to ignore these files?
I considered adding a "CLEAN" tag when uploading the file to make it available instantly. However, will the file still be scanned in this case? Is there a better approach to bypass scanning for trusted files?
The text was updated successfully, but these errors were encountered: