ian-whitestone
commented
3 years ago Initial Exploration
For an MVP, we should take a BYOI (bring your own image) approach and just get zappa deploy and zappa update to deploy a lambda function using an existing Docker Image that complies with these guidelines.
I was able to get a little POC doing this ☝️ :
This is the app.py:
import time
from flask import Flask, jsonify
app = Flask(__name__)
@app.route("/")
def serve():
return jsonify(success=True)
@app.route("/time")
def get_current_time():
return {"time": round(time.time())}Steps
1) I prebuilt a Docker image
FROM amazon/aws-lambda-python:3.8
COPY ./ /var/task/
# Install dependencies with poetry
RUN pip install poetry
RUN POETRY_VIRTUALENVS_CREATE=false poetry install --no-root
CMD [ "handler.lambda_handler" ]The only hack here is you need to have the handler.py (from zappa library) and zappa_settings.py files baked into your docker image. The zappa_settings.py is read in by the handler.py here, and gets generated here in the zip file creation flow.
To get around this, I'm thinking the following may be a simple solution:
- Refactor
handler.pyso it looks forzappa_settings.pyfile, and if that is not there, it looks for all the settings as environment variables. - In zappa flows involving docker, zappa will automatically provide all the contents of
zappa_settings.pyas environment variables that get provided to the Docker image at runtime. That way we don't need to generate anyzappa_settings.pyduring the Docker build step - All that's missing now is adding in
handler.pyin the docker image. I'm thinking this could be solved by having a snippet users can paste in theirDockerfilewhich either downloads a copy ofhandler.pyto their image, or grabs it from their Python libraries folder (since they will have to have installed zappa as a dependency in their image setup)
2) I modified the Zappa code to accept -d / --docker-image-uri as a parameter. If this is provided, it skips all the zip compiling steps, and uses the new lambda create_function API to provide the Docker Image URI.
dmarkey
siran
ArtikUA
programmingwithalex
Earlier this month, AWS announced container image support for AWS Lambda. This means you can now package and deploy lambda functions as container images, instead of using zip files. The container image based approach will solve a lot of headaches caused by the zip file approach, particularly with file sizes (container images can be up to 10GB) and the dependency issues we all know & love.
In an ideal end state, you should be able to call
zappa deploy/zappa update/zappa package(etc.) and specify whether you want to use the traditional zip-based approach or new Docker container based approach. If choosing the latter, Zappa would automatically:For a MVP, we should take a BYOI (bring your own image) approach and just get
zappa deployandzappa updateto deploy a lambda function using an existing Docker Image that complies with these guidelines.