Closed vincentelbrachtbtc closed 7 months ago
While this is indeed a bug, this solution won't support file sizes that are that large for a few reasons.
ClamAV only supports file sizes up to 4Gb
The Lambda function that performs the scan will likely time out on files that are larger than 2.5Gb
Ist there a planned fix for this bug? Is this solution able to scan large files in chunks?
The 7za
needs to be fixed. However I don't think this solution will work for your use case even when the bug is addressed given the limitations of what I mentioned in my previous comment
I need to scan a relatively large files (6-60GB) after being uploaded to s3. ClamScan adds the "IN PROGRESS" tag to the s3 object successfully.
then, the scan Lambda throws the following error:
The files that I am trying to scan are .mbtile files The scan runs successfully on .mbtile files smaller than the threshold of 4GB.
My package.json:
This is how i implemented the Clamscan: