- About
- Installation and Configuration
- Basic Usage
- Advanced Settings
- Advanced Usage
- Keeping The Server Warm
- Serving Static Files / Binary Uploads
- Enabling CORS
- Enabling Secure Endpoints on API Gateway
- Deploying to a Domain With a Let's Encrypt Certificate (DNS Auth)
- Deploying to a Domain With a Let's Encrypt Certificate (HTTP Auth)
- Setting Environment Variables
- Setting Integration Content-Type Aliases
- Catching Unhandled Exceptions
- Using Custom AWS IAM Roles and Policies
- Globally Available Server-less Architectures
- Zappa Guides
- Zappa in the Press
- Sites Using Zappa
- Related Projects
- Hacks
- Contributing
- Support / Development / Training / Consulting
In a hurry? Click to see slides from Serverless SF!
Zappa makes it super easy to deploy all Python WSGI applications on AWS Lambda + API Gateway. Think of it as "serverless" web hosting for your Python web 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.
And finally, Zappa is super easy to use. You can deploy your application with a single command out of the box.
Awesome!
Before you begin, make sure you have a valid AWS account and your AWS credentials file is properly installed.
Zappa can easily be installed through pip, like so:
$ pip install zappa
Please note that Zappa must be installed into your project's virtual environment.
(If you use pyenv and love to manage virtualenvs with pyenv-virtualenv, you just have to call pyenv local [your_venv_name] and it's ready. Conda users should comment here.)
Next, you'll need to define your local and server-side settings.
Zappa can automatically set up your deployment settings for you with the init command:
$ zappa init
This will automatically detect your application type (Flask/Django - Pyramid users see here) and help you define your deployment configuration settings. Once you finish initialization, you'll have a file named zappa_settings.json in your project directory defining your basic deployment settings. It will probably look something like this for most WSGI apps:
{
"dev": { // The name of your environment
"s3_bucket": "lmbda", // The name of your S3 bucket
"app_function": "your_module.app" // The python path to your WSGI application function. In Flask, this is your 'app' object.
}
}or for Django:
{
"dev": { // The name of your environment
"s3_bucket": "lmbda", // The name of your S3 bucket
"django_settings": "your_project.settings" // The python path to your Django settings.
}
}You can define as many environments as your like - we recommend having dev, staging, and production.
Now, you're ready to deploy!
Once your settings are configured, you can package and deploy your application to an environment called "production" with a single command:
$ zappa deploy production
Deploying..
Your application is now live at: https://7k6anj0k99.execute-api.us-east-1.amazonaws.com/production
And now your app is live! How cool is that?!
To explain what's going on, when you call deploy, Zappa will automatically package up your application and local virtual environment into a Lambda-compatible archive, replace any dependencies with versions precompiled for Lambda, set up the function handler and necessary WSGI Middleware, upload the archive to S3, register it as a new Lambda function, create a new API Gateway resource, create WSGI-compatible routes for it, link it to the new Lambda function, and finally delete the archive from your S3 bucket. Handy!
If your application has already been deployed and you only need to upload new Python code, but not touch the underlying routes, you can simply:
$ zappa update production
Updating..
Your application is now live at: https://7k6anj0k99.execute-api.us-east-1.amazonaws.com/production
This creates a new archive, uploads it to S3 and updates the Lambda function to use the new code, but doesn't touch the API Gateway routes.
You can also rollback the deployed code to a previous version by supplying the number of revisions to return to. For instance, to rollback to the version deployed 3 versions ago:
$ zappa rollback production -n 3
Zappa can be used to easily schedule functions to occur on regular intervals. This provides a much nicer, maintenance-free alternative to Celery!
These functions will be packaged and deployed along with your app_function and called from the handler automatically.
Just list your functions and the expression to schedule them using cron or rate syntax in your zappa_settings.json file:
{
"production": {
...
"events": [{
"function": "your_module.your_function", // The function to execute
"expression": "rate(1 minute)" // When to execute it (in cron or rate format)
}],
...
}
}And then:
$ zappa schedule production
And now your function will execute every minute!
If you want to cancel these, you can simply use the unschedule command:
$ zappa unschedule production
And now your scheduled event rules are deleted.
See the example for more details.
Similarly, you can have your functions execute in response to events that happen in the AWS ecosystem, such as S3 uploads, DynamoDB entries, Kinesis streams, and SNS messages.
In your zappa_settings.json file, define your event sources and the function you wish to execute. For instance, this will execute your_module.your_function in response to new objects in your my-bucket S3 bucket. Note that your_function must accept event and context parameters.
{
"production": {
...
"events": [{
"function": "your_module.your_function",
"event_source": {
"arn": "arn:aws:s3:::my-bucket",
"events": [
"s3:ObjectCreated:*" // Supported event types: http://docs.aws.amazon.com/AmazonS3/latest/dev/NotificationHowTo.html#supported-notification-event-types
]
}
}],
...
}
}And then:
$ zappa schedule production
And now your function will execute every time a new upload appears in your bucket!
Similarly, for a Simple Notification Service event:
"events": [
{
"function": "your_module.your_function",
"event_source": {
"arn": "arn:aws:sns:::your-event-topic-arn",
"events": [
"sns:Publish"
]
}
}
]DynamoDB and Kinesis are slightly different as it is not event based but pulling from a stream:
"events": [
{
"function": "replication.replicate_records",
"event_source": {
"arn": "arn:aws:dynamodb:us-east-1:1234554:table/YourTable/stream/2016-05-11T00:00:00.000",
"starting_position": "TRIM_HORIZON", // Supported values: TRIM_HORIZON, LATEST
"batch_size": 50, // Max: 1000
"enabled": true // Default is false
}
}
]You can find more example event sources here.
If you need to remove the API Gateway and Lambda function that you have previously published, you can simply:
$ zappa undeploy production
You will be asked for confirmation before it executes.
If you enabled CloudWatch Logs for your API Gateway service and you don't
want to keep those logs, you can specify the --remove-logs argument to purge the logs for your API Gateway and your Lambda function:
$ zappa undeploy production --remove-logs
If you need to see the status of your deployment and event schedules, simply use the status command.
$ zappa status production
You can watch the logs of a deployment by calling the tail management command.
$ zappa tail production
By default, this will show all log items. You can use the argument --http to filter for HTTP requests, which will be in the Apache Common Log Format.
$ zappa tail production --http
If you don't like the default log colors, you can turn them off with --no-color.
You can execute any function in your application directly at any time by using the invoke command.
For instance, suppose you have a basic application in a file called "my_app.py", and you want to invoke a function in it called "my_function". Once your application is deployed, you can invoke that function at any time by calling:
$ zappa invoke production 'my_app.my_function'
Any remote print statements made and the value the function returned will then be printed to your local console. Nifty!
You can also invoke interpretable Python 2.7 strings directly by using --raw, like so:
$ zappa invoke production "print 1 + 2 + 3" --raw
As a convenience, Zappa can also invoke remote Django 'manage.py' commands with the manage command. For instance, to perform the basic Django status check:
$ zappa manage production showmigrations admin
Obviously, this only works for Django projects which have their settings properly defined.
For commands which have their own arguments, you can also pass the command in as a string, like so:
$ zappa manage production "shell --version"
Commands which require direct user input, such as createsuperuser, should be replaced by commands which use zappa <env> invoke --raw.
(Please note that commands which take over 30 seconds to execute may time-out. See this related issue for a work-around.)
If you want to use Zappa applications on a custom domain or subdomain, you'll need to supply a valid SSL certificate. Fortunately for you, Zappa can automatically create and install free valid SSL certificates using Let's Encrypt!
If your domain is located within an AWS Route 53 Hosted Zone and you've defined domain and lets_encrypt_key (ex: openssl genrsa 2048 > account.key) settings, all you need to do is:
$ zappa certify production
And your domain will be verified, certified and registered!
(Please note that this can take around 45 minutes to take effect the first time your run the command, and around 60 seconds every time after that.)
More detailed instructions are available in this handy guide.
There are other settings that you can define in your local settings to change Zappa's behavior. Use these at your own risk!
{
"dev": {
"api_key_required": false, // enable securing API Gateway endpoints with x-api-key header (default False)
"api_key": "your_api_key_id", // optional, use an existing API key. The option "api_key_required" must be true to apply
"apigateway_enabled": true, // Set to false if you don't want to create an API Gateway resource. Default true.
"assume_policy": "my_assume_policy.json", // optional, IAM assume policy JSON file
"attach_policy": "my_attach_policy.json", // optional, IAM attach policy JSON file
"aws_region": "aws-region-name", // optional, uses region set in profile or environment variables if not set here,
"callbacks": { // Call custom functions during the local Zappa deployment/update process
"settings": "my_app.settings_callback", // After loading the settings
"zip": "my_app.zip_callback", // After creating the package
"post": "my_app.post_callback", // After command has executed
},
"cache_cluster_enabled": false, // Use APIGW cache cluster (default False)
"cache_cluster_size": 0.5, // APIGW Cache Cluster size (default 0.5)
"cloudwatch_log_level": "OFF", // Enables/configures a level of logging for the given staging. Available options: "OFF", "INFO", "ERROR", default "OFF".
"cloudwatch_data_trace": false, // Logs all data about received events.
"cloudwatch_metrics_enabled": false, // Additional metrics for the API Gateway.
"debug": true, // Print Zappa configuration errors tracebacks in the 500
"delete_local_zip": true, // Delete the local zip archive after code updates
"delete_s3_zip": true, // Delete the s3 zip archive
"django_settings": "your_project.production_settings", // The modular path to your Django project's settings. For Django projects only.
"domain": "yourapp.yourdomain.com", // Required if you're using a domain
"environment_variables": {"your_key": "your_value"}, // A dictionary of environment variables that will be available to your deployed app. See also "remote_env". Default {}.
"events": [
{ // Recurring events
"function": "your_module.your_recurring_function", // The function to execute
"expression": "rate(1 minute)" // When to execute it (in cron or rate format)
},
{ // AWS Reactive events
"function": "your_module.your_reactive_function", // The function to execute
"event_source": {
"arn": "arn:aws:s3:::my-bucket", // The ARN of this event source
"events": [
"s3:ObjectCreated:*" // The specific event to execute in response to.
]
}
}
],
"exception_handler": "your_module.report_exception", // function that will be invoked in case Zappa sees an unhandled exception raised from your code
"exclude": ["*.gz", "*.rar"], // A list of regex patterns to exclude from the archive. To exclude boto3 and botocore (available in an older version on Lambda), add "boto3*" and "botocore*".
"extends": "stage_name", // Duplicate and extend another stage's settings. For example, `dev-asia` could extend from `dev-common` with a different `s3_bucket` value.
"http_methods": ["GET", "POST"], // HTTP Methods to route,
"iam_authorization": true, // optional, use IAM to require request signing. Default false. Note that enabling this will override the authorizer configuration.
"authorizer": {
"function": "your_module.your_auth_function", // Local function to run for token validation. For more information about the function see below.
"arn": "arn:aws:lambda:<region>:<account_id>:function:<function_name>", // Existing Lambda function to run for token validation.
"result_ttl": 300, // Optional. Default 300. The time-to-live (TTL) period, in seconds, that specifies how long API Gateway caches authorizer results. Currently, the maximum TTL value is 3600 seconds.
"token_source": "Authorization", // Optional. Default 'Authorization'. The name of a custom authorization header containing the token that clients submit as part of their requests.
"validation_expression": "^Bearer \\w+$", // Optional. A validation expression for the incoming token, specify a regular expression.
},
"integration_response_codes": [200, 301, 404, 500], // Integration response status codes to route
"integration_content_type_aliases": { // For routing requests with non-standard mime types
"application/json": [
"application/vnd.webhooks+json"
]
},
"keep_warm": true, // Create CloudWatch events to keep the server warm.
"keep_warm_expression": "rate(4 minutes)", // How often to execute the keep-warm, in cron and rate format. Default 4 minutes.
"lambda_description": "Your Description", // However you want to describe your project for the AWS console. Default "Zappa Deployment".
"lambda_handler": "your_custom_handler", // The name of Lambda handler. Default: handler.lambda_handler
"lets_encrypt_key": "s3://your-bucket/account.key", // Let's Encrypt account key path. Can either be an S3 path or a local file path.
"lets_encrypt_schedule": "rate(15 days)" // How often to auto-renew Let's Encrypt certificate on the server. Must be set to enable autorenewing, rate or cron syntax.
"log_level": "DEBUG", // Set the Zappa log level. Default INFO, can be one of CRITICAL, ERROR, WARNING, INFO and DEBUG.
"manage_roles": true, // Have Zappa automatically create and define IAM execution roles and policies. Default true. If false, you must define your own IAM Role and role_name setting.
"memory_size": 512, // Lambda function memory in MB
"method_header_types": [ // Which headers to include in the API response. Defaults:
"Content-Type",
"Location",
"Status",
"X-Frame-Options",
"Set-Cookie"
],
"method_response_codes": [200, 301, 404, 500], // Method response status codes to route
"parameter_depth": 10, // Size of URL depth to route. Defaults to 8.
"prebuild_script": "your_module.your_function", // Function to execute before uploading code
"profile_name": "your-profile-name", // AWS profile credentials to use. Default 'default'.
"project_name": "MyProject", // The name of the project as it appears on AWS. Defaults to a slugified `pwd`.
"remote_env": "s3://my-project-config-files/filename.json", // optional file in s3 bucket containing a flat json object which will be used to set custom environment variables.
"role_name": "MyLambdaRole", // Name of Zappa execution role. Default ZappaExecutionRole. To use a different, pre-existing policy, you must also set manage_roles to false.
"s3_bucket": "dev-bucket", // Zappa zip bucket,
"settings_file": "~/Projects/MyApp/settings/dev_settings.py", // Server side settings file location,
"timeout_seconds": 30, // Maximum lifespan for the Lambda function (default 30, max 300.)
"touch": false, // GET the production URL upon initial deployment (default True)
"use_precompiled_packages": false, // If possible, use C-extension packages which have been pre-compiled for AWS Lambda
"vpc_config": { // Optional VPC configuration for Lambda function
"SubnetIds": [ "subnet-12345678" ], // Note: not all availability zones support Lambda!
"SecurityGroupIds": [ "sg-12345678" ]
}
}
}Zappa will automatically set up a regularly occurring execution of your application in order to keep the Lambda function warm. This can be disabled via the 'keep_warm' setting.
Zappa is for running your application code, not for serving static web assets. If you plan on serving custom static assets in your web application (CSS/JavaScript/images/etc.,), you'll likely want to use a combination of AWS S3 and AWS CloudFront.
Your web application framework will likely be able to handle this for you automatically. For Flask, there is Flask-S3, and for Django, there is Django-Storages.
Similarly, you will not be able to accept binary multi-part uploads through the API Gateway. Instead, you should design your application so that binary uploads go directly to S3, which then triggers an event response defined in your events setting! That's thinking serverlessly!
To enable Cross-Origin Resource Sharing (CORS) for your application, follow the AWS "How to CORS" Guide to enable CORS via the API Gateway Console. Don't forget to enable CORS per parameter and re-deploy your API after making the changes!
You can also simply handle CORS directly in your application. If you do this, you'll need to add Access-Control-Allow-Origin, Access-Control-Allow-Headers, and Access-Control-Allow-Methods to the method_header_types key in your zappa_settings.json. See further discussion here.
You can use the api_key_required setting to generate and assign an API key to all the routes of your API Gateway. After redeployment, you can then pass the provided key as a header called x-api-key to access the restricted endpoints. Without the x-api-key header, you will receive a 403. More information on API keys in the API Gateway
You can enable IAM-based (v4 signing) authorization on an API by setting the iam_authorization setting to true. Your API will then require signed requests and access can be controlled via IAM policy. Unsigned requests will receive a 403 response, as will requesters who are not authorized to access the API. Enabling this will override the Authorizer configuration (see below).
If you deploy an API endpoint with Zappa, you can take advantage of API Gateway Authorizers to implement a token-based authentication - all you need to do is to provide a function to create the required output, Zappa takes care of the rest. A good start for the function is the awslabs blueprint example.
If you are wondering for what you would use an Authorizer, here are some potential use cases:
- Call out to OAuth provider
- Decode a JWT token inline
- Lookup in a self-managed DB (for example DynamoDB)
Zappa can be configured to call a function inside your code to do the authorization, or to call some other existing lambda function (which lets you share the authorizer between multiple lambdas). You control the behavior by specifying either the arn or function_name values in the authorizer settings block.
If you want to use Zappa on a domain with a free Let's Encrypt certificate using automatic Route 53 based DNS Authentication, you can follow this handy guide.
If you want to use Zappa on a domain with a free Let's Encrypt certificate using HTTP Authentication, you can follow this guide.
However, it's now far easier to use Route 53-based DNS authentication, which will allow you to use a Let's Encrypt certificate with a single $ zappa certify command.
If you want to set local remote environment variables for a deployment stage, you can simply set them in your zappa_settings.json:
{
"dev": {
...
"environment_variables": {
"your_key": "your_value"
}
},
...
}You can then access these inside your application with:
import os
your_value = os.environ.get('your_key')If your project needs to be aware of the type of environment you're deployed to, you'll also be able to get SERVERTYPE (AWS Lambda), FRAMEWORK (Zappa), PROJECT (your project name) and STAGE (dev, production, etc.) variables at any time.
If you want to use remote environment variables to configure your application (which is especially useful for things like sensitive credentials), you can create a file and place it in an S3 bucket to which your Zappa application has access to. To do this, add the remote_env key to zappa_settings pointing to a file containing a flat JSON object, so that each key-value pair on the object will be set as an environment variable and value whenever a new lambda instance spins up.
For example, to ensure your application has access to the database credentials without storing them in your version control, you can add a file to S3 with the connection string and load it into the lambda environment using the remote_env configuration setting.
super-secret-config.json (uploaded to my-config-bucket):
{
"DB_CONNECTION_STRING": "super-secret:database"
}zappa_settings.json:
{
"dev": {
...
"remote_env": "s3://my-config-bucket/super-secret-config.json",
},
...
}Now in your application you can use:
import os
db_string = os.environ.get('DB_CONNECTION_STRING')By default, Zappa will only route the following MIME-types that are set explicitly via Content-Type header: application/json, application/x-www-form-urlencoded, and multipart/form-data (if the Content-Type header isn't set, application/json will be the default). If a request comes in with Content-Type header set to anything but those 3 values, Amazon will return a 415 status code and a MIME type not supported message. If there is a need to support custom MIME-types (e.g. when a third-party making requests to your API) you can specify aliases for the 3 default types:
zappa_settings.json:
{
"dev": {
...
"integration_content_type_aliases": {
"application/json": ["application/vnd.webhooks+json"]
}
},
...
}Now Zappa will use application/json's template to route requests with MIME-type of application/vnd.webhooks+json. You will need to re-deploy your application for this change to take affect.
By default, if an unhandled exception happens in your code, Zappa will just print the stacktrace into a CloudWatch log. If you wish to use an external reporting tool to take note of those exceptions, you can use the exception_handler configuration option.
zappa_settings.json:
{
"dev": {
...
"exception_handler": "your_module.unhandled_exceptions",
},
...
}The function has to accept three arguments: exception, event, and context:
your_module.py
def unhandled_exception(e, event, context):
send_to_raygun(e, event) # gather data you need and send
return True # Prevent invocation retryYou may still need a similar exception handler inside your application, this is just a way to catch exception which happen at the Zappa/WSGI layer (typically event-based invocations, misconfigured settings, bad Lambda packages, and permissions issues).
By default, AWS Lambda will attempt to retry an event based (non-API Gateway, e.g. CloudWatch) invocation if an exception has been thrown. However, you can prevent this by returning True, as in example above, so Zappa that will not re-raise the uncaught exception, thus preventing AWS Lambda from retrying the current invocation.
By default, the Zappa client will create and manage the necessary IAM policies and roles to execute Zappa applications. However, if you're using Zappa in a corporate environment or as part of a continuous integration, you may instead want to manually manage your remote execution policies instead. (You can specify which local profile to use for deploying your Zappa application by defining the profile_name setting, which will correspond to a profile in your AWS credentials file.)
To manually define the permissions policy of your Zappa execution role, you must define the following in your zappa_settings.json:
{
"dev": {
...
"manage_roles": false, // Disable Zappa client managing roles.
"role_name": "MyLambdaRole", // Name of your Zappa execution role. Default ZappaExecutionRole.
...
},
...
}Ongoing discussion about the minimum policy requirements necessary for a Zappa deployment can be found here.
Click to see slides from ServerlessConf London!
During the init process, you will be given the option to deploy your application "globally." This will allow you to deploy your application to all available AWS regions simultaneously in order to provide a consistent global speed, increased redundancy, data isolation, and legal compliance. You can also choose to deploy only to "primary" locations, the AWS regions with -1 in their names.
To learn more about these capabilities, see these slides from ServerlessConf London.
- Django-Zappa tutorial screencast.
- Using Django-Zappa, Part 1.
- Using Django-Zappa, Part 2: VPCs.
- Building Serverless Microservices with Zappa and Flask
- Zappa で Hello World するまで (Japanese)
- Your guide here?
- Zappa Serves Python, Minus the Servers
- Zappa lyfter serverlösa applikationer med Python
- Interview: Rich Jones on Zappa
- Zappa.io - A simple Zappa homepage
- Zappatista! - The official Zappa blog!
- Mailchimp Signup Utility - A microservice for adding people to a mailing list via API.
- Zappa Slack Inviter - A tiny, server-less service for inviting new users to your Slack channel.
- Serverless Image Host - A thumbnailing service with Flask, Zappa and Pillow.
- Gigger - The live music industry's search engine
- Zappa BitTorrent Tracker - An experimental server-less BitTorrent tracker. Work in progress.
- JankyGlance - A server-less Yahoo! Pipes replacement.
- LambdaMailer - A server-less endpoint for processing a contact form.
- Voter Registration Microservice - Official backup to to the Virginia Department of Elections portal.
- And many more!
Are you using Zappa? Let us know and we'll list your site here!
- lambda-packages - Precompiled C-extension packages for AWS Lambda. Used automatically by Zappa.
- zappa-cms - A tiny server-less CMS for busy hackers. Work in progress.
- flask-ask - A framework for building Amazon Alexa applications. Uses Zappa for deployments.
- zappa-file-widget - A Django plugin for supporting binary file uploads in Django on Zappa.
- zops - Utilities for teams and continuous integrations using Zappa.
Zappa goes quite far beyond what Lambda and API Gateway were ever intended to handle. As a result, there are quite a few hacks in here that allow it to work. Some of those include, but aren't limited to..
- Using VTL to map body, headers, method, params and query strings into JSON, and then turning that into valid WSGI.
- Attaching response codes to response bodies, Base64 encoding the whole thing, using that as a regex to route the response code, decoding the body in VTL, and mapping the response body to that.
- Packing and Base58 encoding multiple cookies into a single cookie because we can only map one kind.
- Turning cookie-setting 301/302 responses into 200 responses with HTML redirects, because we have no way to set headers on redirects.
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 the test writing guide. 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.
To use the git HEAD, you 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.
Do you need help with..
- Porting existing Flask and Django applications to Zappa?
- Building new applications and services that scale infinitely?
- Reducing your operations and hosting costs?
- Adding new custom features into Zappa?
- Training your team to use AWS and other server-less paradigms?
Good news! We're currently available for remote and on-site consulting for small, large and enterprise teams. Please contact [email protected] with your needs and let's work together!
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent