To deploy a Julia program on AWS Lambda currently involves making a custom Docker Image. Recently, Amazon announced the ability to create a Custom Runtime, which lowers the barrier to entry. However, their tutorial is quite lacking and they mostly seem to be partnering with companies?
Does anyone know how difficult it is to make a Custom Runtime? Alternatively, are there any plans to partner with AWS Lambda?
I’ve looked into this a bit; I don’t think it will be too bad to create a julia-based custom runtime, along with “layers” for popular packages. I’ll probably be playing around with creating the julia runtime this week a bit.
Please let me know if there’s any way I can help with this. I looked at the documentation and was absolutely baffled.
I am currently at the AWS London User Group - a report back on re:Invent
The speaker is discussign these custom runtime - GO, Rust, cobol(!) C++
But no mention of Julia. Its a high level overview, so no mention of how hard it is to create a specific one for Julia.
the talk is by Danilo Poccia, Principal Evangelist Serverless, AWS
I will ask if the slides are available.
Count me in for testing too @Seanny123 @quinnj
I talked with Danilo after the meeting, he thinks it should be easy to create a custom runtime for Julia. Not much time to talk, but mentioned a bootstrap process.
I dont know how this would fit in with Julias package structure - maybe we woudl need a different runtime for each mix of packages we need - to be seen when the rubber hits the road of course.
Here is start or some seed?
https://gitlab.com/bibourokushi/try-aws-custom-runtime-for-julia/tree/master
This is a good seed! However, I’m still confused by the set of invocations and how to handle them.
An experimental AWS lambda runtime for Julia can be found in https://github.com/FugroRoames/aws-lambda-julia-runtime