This - if you have to fetch data from or output data to outside of the AWS ecosy... | Hacker News

Hacker Newsnew | past | comments | ask | show | jobs | submit

		hansef on June 16, 2020 \| parent \| context \| favorite \| on: A shared file system for lambda functions This - if you have to fetch data from or output data to outside of the AWS ecosystem, the 512mb /tmp limit pushes you into the additional (relative) complexity of having to run on Fargate pretty quickly. Just had to deal with this for a content ingest job involving pulling a couple GB of data from an FTP server, processing it and pushing it into an RDS database on an hourly basis. Would have been super simple if the file was on S3 already.

jupp0r on June 18, 2020 [–]

Where do you need a distributed file system in this use case? Sounds like all you need is some local scratch space?

scarface74 on June 18, 2020 | [–]

Lambda only gives you 512MB pf local “scratch space”. If it had to provision and de provision gigs of space at each invocation, it would probably cause longer start times and shut down times.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact