3 ms·
It looks like from within an S3 Object Lambda object handler you can do pretty much everything you can in a regular Lambda, including querying other S3 objects
by strogonoff 6y ago
It looks like from within an S3 Object Lambda object handler you can do pretty much everything you can in a regular Lambda, including querying other S3 objects or performing any number of HTTP requests. This opens up some interesting use cases, as well as some extreme footgun scenarios.
- benjaminjackman 6y agoThere is a 60 second limit which seems to be the biggest difference.
- strogonoff 6y agoInteresting, I didn’t spot that. Regular Lambda functions seem to run for up to 15 minutes, so that’s a substantial (and reasonable) limitation.
- jacurtis 6y agoTrue. But the idea is that these functions run in between your server/application requesting the object and AWS returning the object to your server. In other words, they happen synchronously with the object request. So you don't want your server waiting around for 15 minutes on an open request, and most systems won't let you do that anyway (browsers definitely won't). 60 seconds is about as long as you'd want to wait around for your object, and arguably even that is too long. If you need to do some sort of lengthy process to your objects then it should probably be done in some sort of asynchronous queue using a normal Lambda.