Shared Libraries In Github Repo

[BradleyLyman]

The Distillery script bundles the Erlang Runtime System into the deployment zip.
ERTs uses shared libraries for SSL and crypto and as a result the shared libraries have been included in this repo so they are available for use.

This is definitely a bad pattern and should be fixed.

I think the best way to approach this is to move the ERTS and the shared libraries into an AWS Lambda Layer instead of having them be built directly into the zip by Distillery.

[uDude]

Great point. Until that is occurs perhaps we should "ummm, ugly" build a static ERTS to package?

Also, for those ERTS lambda related functions launching the ERTS runtime early in the process would be nice. It is seriously time for an Alexa lambda hook via Erlang/Elixir to AWS/IoT/MQTT, HTTP, CoAp, S3, etc. and custom clouds.

I'd much prefer my Alexa lambda in Elixir over node (not for speed but for clarity and scalability).