Great video, great new feature! Do we have to do anything different if we are using containerized lambda functions? Or will the extra ephemeral storage just “magically” map to the /tmp folder in our container? (Assuming we are using AWS’s standard JS or Python runtime containers as the base images of our dockerfiles)
I loved that moment: "... but, before going like this video! ;-)" and obviously I liked it
yeeey :D
Great video, great new feature! Do we have to do anything different if we are using containerized lambda functions? Or will the extra ephemeral storage just “magically” map to the /tmp folder in our container? (Assuming we are using AWS’s standard JS or Python runtime containers as the base images of our dockerfiles)
Could we load our custom runtimes to the /tmp storage layer as opposed to a lambda layer or a containerized function?
you need to get the runtime from somewhere else and save it then in tmp, either s3 or efs. Or then you can use a layer