After reading through the responses, it sounds like elixir is not a first class citizen (yet?) within AWS lambda, and so it’s not a realistic option without contortions.
I guess my core interest is when to use a self administered, featureful job scheduler like Oban versus externally administered/managed AWS lambda, in a world where there is no penalty or immediate issues with using Elixir in a lambda. That’s too hypothetical for now, so I will revisit in a year or so, if there is more first party or third party support for Elixir in a lambda.
