Serverless Python .zip

<p align="center"> <img src="http://i.imgur.com/oePnHJn.jpg" alt="Zappa Rocks!"/> </p> ## Zappa - Serverless Python [](https://github.com/zappa/Zappa/actions/workflows/ci.yaml) [](https://coveralls.io/github/zappa/Zappa) [](https://pypi.python.org/pypi/zappa) [](https://zappateam.slack.com/) <!-- START doctoc generated TOC please keep comment here to allow auto update --> <!-- DON'T EDIT THIS SECTION, INSTEAD RE-RUN doctoc TO UPDATE --> - [About](#about) - [Installation and Configuration](#installation-and-configuration) - [Running the Initial Setup / Settings](#running-the-initial-setup--settings) - [Basic Usage](#basic-usage) - [Initial Deployments](#initial-deployments) - [Updates](#updates) - [Docker Workflows](#docker-workflows) - [Rollback](#rollback) - [Scheduling](#scheduling) - [Advanced Scheduling](#advanced-scheduling) - [Multiple Expressions](#multiple-expressions) - [Disabled Event](#disabled-event) - [Undeploy](#undeploy) - [Package](#package) - [How Zappa Makes Packages](#how-zappa-makes-packages) - [Template](#template) - [Status](#status) - [Tailing Logs](#tailing-logs) - [Remote Function Invocation](#remote-function-invocation) - [Django Management Commands](#django-management-commands) - [SSL Certification](#ssl-certification) - [Deploying to a Domain With AWS Certificate Manager](#deploying-to-a-domain-with-aws-certificate-manager) - [Deploying to a Domain With a Let's Encrypt Certificate (DNS Auth)](#deploying-to-a-domain-with-a-lets-encrypt-certificate-dns-auth) - [Deploying to a Domain With a Let's Encrypt Certificate (HTTP Auth)](#deploying-to-a-domain-with-a-lets-encrypt-certificate-http-auth) - [Deploying to a Domain With Your Own SSL Certs](#deploying-to-a-domain-with-your-own-ssl-certs) - [Executing in Response to AWS Events](#executing-in-response-to-aws-events) - [Asynchronous Task Execution](#asynchronous-task-execution) - [Catching Exceptions](#catching-exceptions) - [Task Sources](#task-sources) - [Direct Invocation](#direct-invocation) - [Remote Invocations](#remote-invocations) - [Restrictions](#restrictions) - [Running Tasks in a VPC](#running-tasks-in-a-vpc) - [Responses](#responses) - [Advanced Settings](#advanced-settings) - [YAML Settings](#yaml-settings) - [Advanced Usage](#advanced-usage) - [Keeping The Server Warm](#keeping-the-server-warm) - [Serving Static Files / Binary Uploads](#serving-static-files--binary-uploads) - [Enabling CORS](#enabling-cors) - [Large Projects](#large-projects) - [Enabling Bash Completion](#enabling-bash-completion) - [Enabling Secure Endpoints on API Gateway](#enabling-secure-endpoints-on-api-gateway) - [API Key](#api-key) - [IAM Policy](#iam-policy) - [API Gateway Lambda Authorizers](#api-gateway-lambda-authorizers) - [Cognito User Pool Authorizer](#cognito-user-pool-authorizer) - [API Gateway Resource Policy](#api-gateway-resource-policy) - [Setting Environment Variables](#setting-environment-variables) - [Local Environment Variables](#local-environment-variables) - [Remote AWS Environment Variables](#remote-aws-environment-variables) - [Remote Environment Variables](#remote-environment-variables) - [Remote Environment Variables (via an S3 file)](#remote-environment-variables-via-an-s3-file) - [API Gateway Context Variables](#api-gateway-context-variables) - [Catching Unhandled Exceptions](#catching-unhandled-exceptions) - [Using Custom AWS IAM Roles and Policies](#using-custom-aws-iam-roles-and-policies) - [Custom AWS IAM Roles and Policies for Deployment](#custom-aws-iam-roles-and-policies-for-deployment) - [Custom AWS IAM Roles and Policies for Execution](#custom-aws-iam-roles-and-policies-for-execution) - [AWS X-Ray](#aws-x-ray) - [Globally Available Server-less Architectures](#globally-available-server-less-architectures) - [Raising AWS Service Limits](#raising-aws-service-limits) - [Dead Letter Queues](#dead-letter-queues) - [Unique Package ID](#unique-package-id) - [Application Load Balancer Event Source](#application-load-balancer-event-source) - [Endpoint Configuration](#endpoint-configuration) - [Example Private API Gateway configuration](#example-private-api-gateway-configuration) - [Cold Starts (Experimental)](#cold-starts-experimental) - [Zappa Guides](#zappa-guides) - [Zappa in the Press](#zappa-in-the-press) - [Sites Using Zappa](#sites-using-zappa) - [Related Projects](#related-projects) - [Hacks](#hacks) - [Contributing](#contributing) - [Using a Local Repo](#using-a-local-repo) <!-- END doctoc generated TOC please keep comment here to allow auto update --> ## About <p align="center"> <a href="https://htmlpreview.github.io/?https://raw.githubusercontent.com/Miserlou/Talks/master/serverless-sf/big.quickstart.html"><img src="http://i.imgur.com/c23kDNT.png?1" alt="Zappa Slides"/></a> </p> <p align="center"> <i>In a hurry? Click to see <a href="https://htmlpreview.github.io/?https://raw.githubusercontent.com/Miserlou/Talks/master/serverless-sf/big.quickstart.html">(now slightly out-dated) slides from Serverless SF</a>!</i> </p> **Zappa** makes it super easy to build and deploy server-less, event-driven Python applications (including, but not limited to, WSGI web apps) on AWS Lambda + API Gateway. Think of it as "serverless" web hosting for your Python apps. That means **infinite scaling**, **zero downtime**, **zero maintenance** - and at a fraction of the cost of your current deployments! If you've got a Python web app (including Django and Flask apps), it's as easy as: ``` $ pip install zappa $ zappa init $ zappa deploy ``` and now you're server-less! _Wow!_ > What do you mean "serverless"? Okay, so there still is a server - but it only has a _40 millisecond_ life cycle! Serverless in this case means **"without any permanent infrastructure."** With a traditional HTTP server, the server is online 24/7, processing requests one by one as they come in. If the queue of incoming requests grows too large, some requests will time out. With Zappa, **each request is given its own virtual HTTP "server"** by Amazon API Gateway. AWS handles the horizontal scaling automatically, so no requests ever time out. Each request then calls your application from a memory cache in AWS Lambda and returns the response via Python's WSGI interface. After your app returns, the "server" dies. Better still, with Zappa you only pay for the milliseconds of server time that you use, so it's many **orders of magnitude cheaper** than VPS/PaaS hosts like Linode or Heroku - and in most cases, it's completely free. Plus, there's no need to worry about load balancing or keeping servers online ever again. It's great for deploying serverless microservices with frameworks like Flask and Bottle, and for hosting larger web apps and CMSes with Django. Or, you can use any WSGI-compatible app you like! You **probably don't need to change your existing applications** to use it, and you're not locked into using it. Zappa also lets you build hybrid event-driven applications that can scale to **trillions of events** a year with **no additional effort** on your part! You also get **free SSL certificates**, **global app deployment**, **API access management**, **automatic security policy generation**, **precompiled C-extensions**, **auto keep-warms**, **oversized Lambda packages**, and **many other exclusive features**! And finally, Zappa is **super easy to use**. You can deploy your application with a single command out of the box! __Awesome!__ <p align="center"> <img src="http://i.imgur.com/f1PJxCQ.gif" alt="Zappa Demo Gif"/> </p> ## Installation and C