New for AWS Lambda – Container Image Support
aws.amazon.com
New for AWS Lambda – Container Image Support
1–10 of 94 posts
Re: New for AWS Lambda – Container Image Support
#2This feels like a pretty monumental change - my team(s) have historically avoided Lambda specifically because the local dev flow is such a pain and/or open to interpretation, but local dev tooling for building and working with containers is great. At the same time, creating task definitions for one-off tasks in ECS or similar is also kind of a weird workflow if the task is shortlived or event-driven.
Using an actual container orchestration platform when you need it, and a lambda to run the same container image one-off when you don't need orchestration, feels like a best of both worlds.
I like the idea of "serverless" being more "your packaged execution environment, running with no regard for the underlying host" than "your code, running with no regard for the underlying execution environment".
EDIT: Disregard.... see the AWS team's responses in this topic for the full story, its not quite as convenient as anything packaged via standard container being able to run on Lambda
Re: New for AWS Lambda – Container Image Support
#3Was already working through porting my startup’s web app from docker to lambda via layers and such, but it was a hassle. Then I read today about the 1ms billing and got motivated. THEN I see this about running containers, my life just got much easier. What a time to be alive!
Re: New for AWS Lambda – Container Image Support
#4This is pretty cool, to me it looks like it's moving towards Google Cloud Run's feature set.
Re: New for AWS Lambda – Container Image Support
#5This is pretty cool, to me it looks like it's moving towards Google Cloud Run's feature set.
One small note - Cloud Run is KNative as a service. Lambda is divorced from Kubernetes.
Personal opinion - I prefer Lambda over KNative. KNative feels like more of a shoehorn into Kubernetes than most other projects. Lambda feels more mature.
Still glad to see this move, regardless.
Re: New for AWS Lambda – Container Image Support
#6This is great. I recently went through the exercise of deploying a periodic lambda function using AWS SAM. The development workflow was great, except when I needed binary dependencies for the MSSQL database driver. Learning and using Lambda layers was cumbersome and the bulk of the dev time. This change will make the lives of engineers in docker shops much easier.
Re: New for AWS Lambda – Container Image Support
#7This is pretty cool, to me it looks like it's moving towards Google Cloud Run's feature set.
One small note - Cloud Run is KNative as a service. Lambda is divorced from Kubernetes. Personal opinion - I prefer Lambda over KNative. KNative feels like more of a shoehorn into Kubernetes than most other projects. Lambda feels more mature. Still glad to see this move, regardless.
How so? With Google Cloud Run, you don't really interact with Knative or Kubernetes, so the underlying platform is a non-issue.
Re: New for AWS Lambda – Container Image Support
#8This is pretty cool, to me it looks like it's moving towards Google Cloud Run's feature set.
One small note - Cloud Run is KNative as a service. Lambda is divorced from Kubernetes. Personal opinion - I prefer Lambda over KNative. KNative feels like more of a shoehorn into Kubernetes than most other projects. Lambda feels more mature. Still glad to see this move, regardless.
There are two versions of Cloud Run. The fully-managed cloud-only variant is actually an API skin over Google App Engine. The "for Anthos" (née "for GKE") variant is Knative[0] in both API and sourcecode.
AWS could plausibly do exactly the same thing: provide a skin over Lambda that speaks Knative.
I think Amazon's and Microsoft's reluctance to wade into Knative has been wariness about Google's intentions. And maybe 6 months ago I would have said "fair enough, I would be cautious too". But the recent update to Knative's governance model largely resolves the problem, in my view. I would very much like to see AWS and MS involvement.
[0] "Knative" is the correct spelling, FWIW.
Disclosure: I work for VMware, which participates in Knative development.
I also, like, wrote a book about it.
Re: New for AWS Lambda – Container Image Support
#9This feels like a pretty monumental change - my team(s) have historically avoided Lambda specifically because the local dev flow is such a pain and/or open to interpretation, but local dev tooling for building and working with containers is great. At the same time, creating task definitions for one-off tasks in ECS or similar is also kind of a weird workflow if the task is shortlived or event-driven. Using an actual…
Worth noting this isn't bring any application and publish as AWS Lambda, but rather build from a specific Lambda base image and package your Lambda code into it. Fargate likely closer to what you are describing here
Re: New for AWS Lambda – Container Image Support
#10This is pretty cool, to me it looks like it's moving towards Google Cloud Run's feature set.
That was my initial thought too, but looks like these lambdas have to derive from a specific set of Lambda base images. Cloud Run lets your publish ANY docker container from any base image. So this feels much more like a deployment and development feature of Lambdas and not "run any container as a Lambda"