What is this?
Zappa is a tool that packages and deploys Python WSGI web applications (built with Flask, Django, Bottle or Pyramid) to run serverlessly on AWS Lambda behind API Gateway, with no servers to manage.
Is Zappa a web framework or a deployment tool for existing apps?
It is a deployment/packaging CLI, not a framework. You keep writing your app in Flask, Django, Bottle or Pyramid as usual and Zappa handles shipping it to Lambda.
How do I deploy my app with Zappa?
Install it with pip, run 'zappa init' to generate a config for your project, then 'zappa deploy' (or 'zappa update' for subsequent deploys) to push it to AWS Lambda and API Gateway.
Do I need an AWS account to use it?
Yes, Zappa deploys to AWS Lambda and API Gateway, so you need AWS credentials configured locally before deploying.
Is this GitHub repo still where active development and releases happen?
No, this repository was the original home of Zappa but releases after version 0.52.0 are now published from a different location, so check that successor project for the latest fixes.
Which Python web frameworks work with Zappa?
It supports WSGI-compatible frameworks: Flask, Django, Bottle and Pyramid, as listed in the project's own topics.
Why use Lambda instead of a normal server for a Flask or Django app?
Lambda scales automatically and you only pay per request, so Zappa lets existing WSGI apps run without provisioning or managing any servers.
Can I still use my existing Django or Flask codebase unchanged?
Yes, Zappa wraps your existing WSGI app; you generally don't need to rewrite the app itself, just configure and deploy it with Zappa's CLI.
What are similar projects?
chalice, examples, serverless, localstack, encore, awesome-aws, pulumi, caprover
Which topics is it in?
aws-lambda, lambda, flask, django, api-gateway, serverless, aws, deployment, deprecated, cloud, devops, backend