Skip to content
This repository has been archived by the owner on Jun 20, 2023. It is now read-only.

Support using EFS for storage #154

Open
shawnjohnson opened this issue Jan 22, 2021 · 6 comments
Open

Support using EFS for storage #154

shawnjohnson opened this issue Jan 22, 2021 · 6 comments

Comments

@shawnjohnson
Copy link

The new EFS storage feature for Lambda opens up some interesting options to work around the Large file issue, as well as virus definitions. We are currently trying to figure out a way around running out of space while scanning a 300 MB file. It seems like it could be possible to change the code around this line to allow an alternative path to be provided, perhaps via new configuration option?

@jny986
Copy link

jny986 commented Mar 4, 2021

I would also like to see the use of EFS for both file storage for scanning as well as for the storage of virus definitions.

@shawnjohnson
Copy link
Author

@jny986 - I am curious what the use case for storing virus definitions on EFS would be? The path for virus definitions is already an Configuration option with the AV_DEFINITION_PATH Environment variable. I imagine you could use that now without any code changes?

@tengfone
Copy link

Hi @shawnjohnson , did you manage to route the path to EFS storage instead of using the tmp lambda storage? Thanks

@shawnjohnson
Copy link
Author

@tengfone - We added the ability to override the default path of /tmp. Then the Lambda function is configured with an EFS volume, and the path is specified as an Environment variable (AV_SCAN_PATH). Here is the bulk of the changes made - erulemaking@39a9862

@tengfone
Copy link

@shawnjohnson Thank you v much! Will be using that!

@robbrad
Copy link

robbrad commented Feb 18, 2022

Can this be PR'ed into the main repo - seams like a great addition

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants