New for AWS Lambda – Container Image Support

Post by [deleted] » Wed, Dec 02, 2020, 2:35 AM UTC

davidbanham wrote: post #51

mwcampbell wrote: post #48

Earlier quoted context omitted.

> but what you are looking for already exists I'd say, and is Fargate. IIUC though, Fargate doesn't have "scale to zero" like Lambda and API Gateway. Then again, IMO, scale to zero and the associated cold starts probably aren't the best fit for handling HTTP requests that are waiting for an answer right now.

Cloud Run on GCP is the “run any container” solution that this isn’t. It scales to zero, responds immediately to an incoming http request and can handle up to 50 concurrent requests out of the one invocation for no additional cost.

Post by nojvek » Wed, Dec 02, 2020, 2:41 AM UTC

munns wrote: post #30

tebbers wrote: post #4

This is pretty cool, to me it looks like it's moving towards Google Cloud Run's feature set.

Not entirely. This is something we've been thinking about for years now and is really about tooling and developer workflow. That is where the biggest benefit is for this. - Chris - Serverless@AWS

Post by stephanos2k » Wed, Dec 02, 2020, 5:13 AM UTC

munns wrote: post #46

nlg wrote: post #37

Earlier quoted context omitted.

Thanks for coming here to answer questions. Much appreciated! Does each new Lambda cold start pull the entire image from the repo? Or if I derive from Lambda base images am I likely to get some of the layers already cached? I'm trying to think about how the data transfer costs are going to each time the Lambda is instantiated. I didn't take this into account with Fargate and got burned when trying to trigger images o…

There's a few things at play. Functions will still stay warm inbetween invocations and will keep local any data already in the worker. We also maintain a couple different levels of cache so as to not hit ECR often. I know we've got a few blog posts coming out over the next couple weeks on this new feature, and each tells a few bits and pieces about the story. Depending on volume you'll probably find that Lambda will…

Post by richardanaya » Wed, Dec 02, 2020, 5:41 AM UTC

Post by saurik » Wed, Dec 02, 2020, 8:05 AM UTC

munns wrote: post #11

Hey everyone, we're really excited about this feature launch, and I wanted to come in to clarify any misconceptions. With this capability you can now package Lambda functions using familiar container image tools (Dockerfile, cli tools, build systems) but you still need to code them for the event model, have a handler, etc. It's a big improvement, but its not "run any container in Lambda". Either way, hope you go and…