1 Antwort
- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
0
After the two minutes between executions, Lambda may reuse an existing container (execution context) or create a new one; you cannot rely on a new container always being created. If the container is reused, the /tmp
folder will be populated already. That said, if a previous execution is still running, a new container will be created as to not interfere with the existing function execution (e.g. if you have 100 executions of a function running at the same time, there will be 100 separate containers for them).
beantwortet vor 2 Jahren
Relevanter Inhalt
- AWS OFFICIALAktualisiert vor 8 Monaten
- AWS OFFICIALAktualisiert vor 2 Jahren
- AWS OFFICIALAktualisiert vor 10 Monaten
Thanks for replying so swiftly Justin!
Ok so can I safely assume that a new container will be used if there is a upload from lambda's tmp to S3 ongoing by the time the 2minutes are reached?
It may be smarter to have two separate lambdas, one that passes the download orders to a queue and that has an EventBridge and one that takes its time to download each item added to the queue (and so without a CRON for this second one). Does having multiple containers running for the same lambda mean higher costs as well? I mean compare to the alternative solution I mention just above.
Cheers