> We’ve been able to use custom runtimes ourselves for a while, and via the magic of Docker container images we can basically make Lambda run whatever the heck

> We’ve been able to use custom runtimes ourselves for a while, and via the magic of Docker container images we can basically make Lambda run whatever the heck we want it to. Unfortunately, building our own Python runtimes at home isn’t sustainable as a customer Custom runtimes with Docker images solves so many issues with Lambda. Artifact management for free and the ability to run whatever language/applicaiton you want on Lambda. It works well, it's simple, it's portable. I can run my containers I deploy to Lambda on Lambda, Kubernetes, my local machine, pretty much anywhere if I abstract the AWS services i use. Building a Python Docker image isn't sustainable as a customer? I don't understand that as most people package apps as containers already as a standard unit of deployment.Most large companies maintain their own base images. It looks like the only in-convenience for Python is doing `pip install awslambdaric` With custom runtime Docker images I think AWS was smart, removing AWS maintenance as the limiting factor to let users have pretty much full control of the runtime, fairly trivially with tools they already know.