1 Answer
- Newest
- Most votes
- Most comments
0
The /tmp
directory on each Lambda function is private to that function - so your cold boot code would need to copy the files to that directory on first boot. By default, Lambda supports 512 MB of temporary storage but that can be increased.
If you wanted to store the files externally, consider using EFS with your Lambda function.
Relevant content
- Accepted Answerasked 14 days ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
thanks @Brettski-AWS. I am already doing that, but unfortunately my response time is too slow. As I said, it is very IO intensive and i have a large dataset. I dont mind a very long cold boot, but once it is up it will get a bunch of quick requests in succession. I had good luck with setting it up with an EC2 instance where i copy all the data from disk to a ram drive, but just a large instance up all the time for a bursty workload doesn't make sense. if i can create a ramdrive / tmpfs on Lambda, that would be the best.