Zappa | Serverless Python | Serverless library

 by   zappa Python Version: 0.58.0 License: MIT

kandi X-RAY | Zappa Summary

kandi X-RAY | Zappa Summary

Zappa is a Python library typically used in Telecommunications, Media, Media, Entertainment, Serverless applications. Zappa has no bugs, it has no vulnerabilities, it has build file available, it has a Permissive License and it has medium support. You can install using 'pip install Zappa' or download it from GitHub, PyPI.

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!.

            kandi-support Support

              Zappa has a medium active ecosystem.
              It has 2483 star(s) with 311 fork(s). There are 34 watchers for this library.
              There were 1 major release(s) in the last 12 months.
              There are 445 open issues and 661 have been closed. On average issues are closed in 137 days. There are 41 open pull requests and 0 closed requests.
              It has a neutral sentiment in the developer community.
              The latest version of Zappa is 0.58.0

            kandi-Quality Quality

              Zappa has 0 bugs and 0 code smells.

            kandi-Security Security

              Zappa has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.
              Zappa code analysis shows 0 unresolved vulnerabilities.
              There are 0 security hotspots that need review.

            kandi-License License

              Zappa is licensed under the MIT License. This license is Permissive.
              Permissive licenses have the least restrictions, and you can use them in most projects.

            kandi-Reuse Reuse

              Zappa releases are available to install and integrate.
              Deployable package is available in PyPI.
              Build file is available. You can build the component from source.
              Installation instructions, examples and code snippets are available.
              It has 10427 lines of code, 426 functions and 37 files.
              It has high code complexity. Code complexity directly impacts maintainability of the code.

            Top functions reviewed by kandi - BETA

            kandi has reviewed Zappa and discovered the below as its top functions. This is intended to give you an instant insight into Zappa implemented functionality, and help decide if they suit your requirements.
            • Creates a new API Gateway
            • Get patch operation
            • Return the stage configuration
            • Updates the lambda function
            • Register callback function
            • Check if the virtual environment is active
            • Execute a lambda function
            • Invoke a lambda function
            • Send a message to Lambda
            • Send a message
            • Run zappa
            • Handles the command line arguments
            • Check if Zappa is available
            • Check if a new version is available
            • Load a zip file from S3
            • Update the configuration of a stage
            • Format a log entry
            • Format a log message
            • Route a SNS task to a message
            • Get the status of an event source
            • Route the given event to the appropriate route
            • Adds a deny method to the ban
            • Decorator to tag a function as a task
            • Shortcut method to add a new HTTP method
            • Define a deny method
            • Shortcut to add an Allow Method
            Get all kandi verified functions for this library.

            Zappa Key Features

            No Key Features are available at this moment for Zappa.

            Zappa Examples and Code Snippets

            copy iconCopy
            # Zappa 설치
            (venv) $ pip install zappa
            Successfully installed ... zappa-0.51.0 zipp-3.1.0
            # 명령어들을 확인해봅니다.
            (venv) $ zappa --help
            usage: zappa [-h] [-v] [--color {auto,never,always}]
            Epsagon Tracing for Python,Frameworks,Zappa
            Pythondot img2Lines of Code : 15dot img2License : Permissive (MIT)
            copy iconCopy
            from zappa.handler import lambda_handler
            import epsagon
            # Your code is here
            epsagon_handler = epsagon.lambda_wrapper(lambda_handler)
            HTMLdot img3Lines of Code : 13dot img3License : Permissive (MIT)
            copy iconCopy
            title: The Title
            author: Your Name
            date-created: 01-01-2016
            format: markdown
            # Title title title 
            **Body** body body body.
            $ ./
            $ zappa deploy production
            How do I resolve database migration error due to changed migration filename?
            Pythondot img4Lines of Code : 3dot img4License : Strong Copyleft (CC BY-SA 4.0)
            copy iconCopy
            python migrate myapp 0017 --fake # Move to 17 without removing changes done by 18
            python migrate myapp 0018 --fake # 18 is already applied, so just migrate with the new filename
            ImproperlyConfigured: Error loading psycopg2 module: No module named 'psycopg2._psycopg' zappa
            Pythondot img5Lines of Code : 12dot img5License : Strong Copyleft (CC BY-SA 4.0)
            copy iconCopy
            FROM amazonlinux:2.0.20200207.1
            RUN cd /opt && \
                yum install -y gcc openssl-devel bzip2-devel libffi-devel wget tar gzip make && \
                wget && \
            When does a new python session in AWS is created?
            Pythondot img6Lines of Code : 12dot img6License : Strong Copyleft (CC BY-SA 4.0)
            copy iconCopy
  'Cold Start')
            CONNECTION = None
            def my_handler(event, context):
                global CONNECTION
                if CONNECTION is None:
          'Initializing Connection')
                    CONNECTION = make_connection()
            ModuleNotFound cause 502 deploying django with zappa on aws lambda
            Pythondot img7Lines of Code : 7dot img7License : Strong Copyleft (CC BY-SA 4.0)
            copy iconCopy
            Allow "ObjectCreated" event notification from my zappa app
            Pythondot img8Lines of Code : 11dot img8License : Strong Copyleft (CC BY-SA 4.0)
            copy iconCopy
                  "Action": [
                  "Effect": "Allow",
                  "Resource": [
            Iterate nested JSON in python to get tall dataframe
            Pythondot img9Lines of Code : 14dot img9License : Strong Copyleft (CC BY-SA 4.0)
            copy iconCopy
            df = pd.DataFrame(s).explode("columns").reset_index(drop=True) #s being your json
            print (pd.concat([df["name"],
            Iterate nested JSON in python to get tall dataframe
            Pythondot img10Lines of Code : 31dot img10License : Strong Copyleft (CC BY-SA 4.0)
            copy iconCopy
            import json
            with open('temp.json') as json_file:
                data = json.load(json_file)
            df = pd.json_normalize(data)
            df = df.explode(column="columns").reset_index()
            df["partitions"] = df["partitions"].apply(lambda x: x[0])
            temp = df["columns"].

            Community Discussions


            Zappa: No module named '_cffi_backend'
            Asked 2022-Feb-09 at 11:13

            I recently uploaded an Django application with the use off Zappa, which was running perfectly fine.

            Now, I wanted to update this application, and It suddenly gives me this error: (The changes I made wasn't really that much, removed a blank=True in my



            Answered 2022-Feb-09 at 11:13

            Don't exactly know what went wrong but I got it fixed by:

            1. completly removing my virtual environment
            2. creating a new one.
            3. installing packages with pip install -r requirements.txt --no-cache-dir

            the --no-cache-dir was really important adding.



            Troubleshooting custom domain using Zappa
            Asked 2022-Jan-17 at 21:16

            I’m doing some troubleshooting for a custom domain (purchased via Google). I’ve updated the custom resource record in Google, done the route 53 + AWS cert manager steps, and ran zappa certify (as well as zappa update). My first thought… is it supposed to show the AWS link after the custom domain: e.g.,



            Answered 2022-Jan-17 at 21:16

            Resolved my own issue ... simple mistake.

            In Google Domains, I was using 'Default Name Servers' with CNAME customer records. Instead, I needed to use 'Custom Name Servers' and activated the 4 names servers from route 53. Hopefully this helps anyone who encounters similar troubleshooting w AWS/Google/Zappa!



            Zappa Django: instead of re-querying the database, it uses an outdated in-memory cache. Can this behavior be changed?
            Asked 2021-Nov-30 at 15:50

            In my project, I use Django as a frontend only. All backend logic is several AWS Lambda Python functions coordinated by the state machine. The database is SQLite in the S3 bucket. I use django_s3_storage and django_s3_sqlite. My backend functions change the number of model instances and their details in the SQLite database. I'd like those changes to be reflected by the Django frontend ASAP. However, it does not happen. I see only the outdated in-memory cache.

            I have tried several things.

            My initial view:



            Answered 2021-Nov-30 at 15:50

            Your Django Lambda container instances will download the SQLite DB on load and then will cache the file locally until the Lambda container is shut down by AWS. This is done automatically by the django_s3_sqlite package.

            Since you are making writes to the database using a separate backend system, the Django Lambda container instances are not aware of changes and thus will not re-download the SQLite DB from S3. The functions you list are all Django based caching and will have no effect.

            If you want the Django app to reflect DB changes in a faster time period, you will need to migrate to a centralized database such as PostgreSQL on RDS or DynamoDB.



            Use Cloudfront to remove {stage} from custom domain url
            Asked 2021-Oct-12 at 19:01

            I have a flask app deployed to AWS Lambda via zappa. Zappa creates an AWS rest endpoint such as works perfectly when directly entered into the browser. But, when I use Cloudfront to associate this end point to my custom domain,, I get a 404 error in the response for any assets stored in a subfolder. The reason is because Cloudfront is serving urls such as


            instead of


            Also, this works:

            But this does not:

            So, somehow, I need Cloudfront to associate with instead of

            My Cloudfront distribution has the following parameters:



            Answered 2021-Oct-10 at 05:36

            There is an option that you are able to add your stageName to make your URL to be accessible without it.


            Go to your CloudFront's Distribution, edit your Origin which points to API Gateway URL.

            • Find the Origin path option
            • Place your stageName into it (my example is dev stage) so it should be /dev (need to have / at prefix)

            Then click Save changes and wait for the deployment around 5 minutes. And try to access it as you would love to



            AWS Lambda - removing Python packages to speed up deployment and execution
            Asked 2021-Sep-17 at 01:28

            Working to update an AWS Lambda function that relies on Flask / zappa that was originally written by another programmer. If Python modules are not imported / used by the scripts that are running in Lambda, can I remove them without any problem from requirements.txt?

            The example file provided by AWS seems to have very few requirements. I just want to make sure that Cloudwatch continues to work and I'm not deleting things that AWS depends on implicitly.

            Some of the packages that I am considering removing (since not imported by the Python scripts) include:

            • durationpy
            • pyrsistent
            • placebo
            • pytz
            • pycparser
            • troposphere
            • boto3

            i.e. removing pyarrow and scikit-learn cut the redeploy time down from 3 minutes to 2 minutes. AWS Lambda also uses less RAM over shorter duration to execute.



            Answered 2021-Sep-17 at 01:28

            It's hard to say as the dependencies vary across applications.

            As far as I know, scikit-learn is a huge library and is not used by AWS. However, if your application or another package in your application uses it as a dependency, removing it might break your application.

            Similarly pyarrow is also used by many packages. Some of the packages of your application could be using it internally.

            I'm not sure but boto3 can also be removed as it's always available by default by AWS. But you might want to keep it since you'll be needing it for running the application locally.

            For all other packages, I suggest you create a dependency tree of your packages using pipdeptree This will serve as starting point to determine which can could be removed.



            Force Zappa to use API Gateway HTTP API instead of REST
            Asked 2021-Sep-07 at 12:57

            I want to use AWS API Gateway HTTP API instead of old REST with my lambda functions, for pricing reasons.

            Difference here:

            What is the option in Zappa for this?



            Answered 2021-Sep-07 at 12:57

            As of Sept 2021, there is no support for HTTP API Gateways. There is an issue created to add support here:



            Zappa Django one lambda per app in a monorepo
            Asked 2021-Aug-08 at 19:03

            My Django REST API is composed of multiples apps, one app per resource like that:



            Answered 2021-Aug-08 at 19:03

            I suggest you add a stage per app in your zappa_settings.json file. Then you can deploy each stage independently.

            See the documentation for exact formatting.



            When installing Pipfile there is a collision of dependency version of werkzeug, werkzeug<1.0 from zappa, werkzeug>2.0 from flask
            Asked 2021-Jul-15 at 13:10

            When installing the Pipfile i'm getting the error 'ERROR: Could not find a version that matches werkzeug<1.0,>=2.0'

            There are incompatible versions in the resolved dependencies: werkzeug<1.0 (from zappa==0.51.0) werkzeug>=2.0 (from flask==2.0.1)

            MY Pipfile contains (among other stuff):



            Answered 2021-Jul-15 at 11:51

            your zappa version is 0.51.0 which was released on March 2020 and your flask version is 2.0.1 which was released on May 2021 and their sub dependencies are different. I fixed the issue by downgrading the flask version by specifying version 1.1.4 in pipfile. flask = "==1.1.4"



            Zappa deploy fails with AttributeError: 'Template' object has no attribute 'add_description'
            Asked 2021-Jul-15 at 09:53

            Since a few days ago, zappa deploy fails with the following error (zappa version 0.50.0):



            Answered 2021-Jul-15 at 09:53

            Since version 3.0.0, the package troposphere removed the deprecated Template methods (see the changelog).

            Breaking changes: * Python 3.6+ (Python 2.x and earlier Python 3.x support is now deprecated due to Python EOL) * Remove previously deprecated Template methods.

            The above issue can be fixed by adding troposphere<3 in the requirements file.



            Is it possible to integrate an old/legacy Django application into Zappa for serverless integration?
            Asked 2021-Jun-27 at 21:06

            I am trying to find a way to integrate our company's Django Web app into Zappa so we can go completely serverless with our REST API. The problem is that our app has existed for several years, making it a lot heavier than the brand new apps that all of these Zappa tutorials init over. Is there a format that Zappa requires for integrating an old Django app into its framework? I have no wait of knowing how much refactoring will be required for Zappa to know how to transition our API into lambda functions. When I tried running Zappa deploy in our root directory, I got the following error, which probably means our app is poorly optimized for the Zappa system:



            Answered 2021-Jun-27 at 21:06

            One of the primary uses of Zappa is to allow the migration of an existing Django project into AWS Lambda. So moving your REST API to be serverless is an excellent use case for Zappa. In addition, Zappa generally is compatible with older versions of Django.

            The issue you are encountering is that AWS Lambda functions must be under 50MB compressed and 250MB uncompressed.

            Zappa offers a workaround using the slim_handler option that allows your project to approach 512MB uncompressed.

            To determine how much disk space your current project requires uncompressed, you may run the following Zappa command:


            Community Discussions, Code Snippets contain sources that include Stack Exchange Network


            No vulnerabilities reported

            Install Zappa

            Zappa can easily be installed through pip, like so:. Please note that Zappa must be installed into your project's virtual environment. The virtual environment name should not be the same as the Zappa project name, as this may cause errors. Next, you'll need to define your local and server-side settings.


            This project is still young, so there is still plenty to be done. Contributions are more than welcome!. Please file tickets for discussion before submitting patches. Pull requests should target master and should leave Zappa in a "shippable" state if merged. If you are adding a non-trivial amount of new code, please include a functioning test in your PR. For AWS calls, we use the placebo library, which you can learn to use in their README. The test suite will be run by Travis CI once you open a pull request. Please include the GitHub issue or pull request URL that has discussion related to your changes as a comment in the code (example). This greatly helps for project maintainability, as it allows us to trace back use cases and explain decision making. Similarly, please make sure that you meet all of the requirements listed in the pull request template. Please feel free to work on any open ticket, especially any ticket marked with the "help-wanted" label. If you get stuck or want to discuss an issue further, please join our Slack channel, where you'll find a community of smart and interesting people working dilligently on hard problems. Zappa does not intend to conform to PEP8, isolate your commits so that changes to functionality with changes made by your linter. To use the git HEAD, you probably can't use pip install -e . Instead, you should clone the repo to your machine and then pip install /path/to/zappa/repo or ln -s /path/to/zappa/repo/zappa zappa in your local project.
            Find more information at:

            Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items

            Find more libraries
          • PyPI

            pip install zappa

          • CLONE
          • HTTPS


          • CLI

            gh repo clone zappa/Zappa

          • sshUrl


          • Stay Updated

            Subscribe to our newsletter for trending solutions and developer bootcamps

            Agree to Sign up and Terms & Conditions

            Share this Page

            share link