New for AWS Lambda – Container Image Support

Post by solarengineer » Wed, Dec 02, 2020, 11:27 AM UTC

scoopertrooper wrote: post #76

simonw wrote: post #75

Earlier quoted context omitted.

I'd expect that I would send a Dockerfile once and have that compiled into a lambda for me which would then run in perpetuity unless I sent over a fresh Dockerfile to over-write that deployment, so non-reproducible Dockerfiles wouldn't bother me. I'm OK with developers needing to understand that a Dockerfile may build differently each time if they don't take extra steps to prevent that (like pinning installed version…

This doesn't seem to me like something that should be a core part of the lambda product, but maybe some sort of simplified build pipeline service that has Lambda as a target.

Post by ngrilly » Wed, Dec 02, 2020, 9:17 PM UTC

saurik wrote: post #88

ngrilly wrote: post #50

Earlier quoted context omitted.

Why does the lambda container has to pull events from the lambda runtime using an HTTP GET request, instead of having the runtime push the events with an HTTP POST?

How would the runtime know for sure when the container was ready to accept the request? The lambda model--with the container pulling the events instead of them being pushed to it--seems like the correct way to model the concurrency.