Serverless Django with Zappa Course Overview

Video Course - Serverless Django Applications With Lambda

Let's explore what Serverless is and isn't

Why Go Serverless? Understanding Zappa's Benefits

About the Author

Class Details

Introduction

We establish the necessary AWS credentials

Creating and Configuring an AWS Account for Zappa Deployment

Let's create a reliable development environment

How to Set Up an AWS Lambda-Like Environment with Docker

Understanding the Basics of Django and Zappa Development

Activating the Environment

Getting Started

Setting Up a Zappa Development Environment

How to Deploy a Django App to the Cloud with AWS Lambda

Serverless projects sometimes need changes

What You Need to Know About AWS Lambda Deployments

Dive into Zappa

Serving static files is different in Serverless

Django Tutorial - What are Static Files?

Two Ways to Handle Django Static Files

Serve static files directly from your project

Configuring WhiteNoise with Django for Static Files

How to Set Up S3 Buckets to Serve Static Files from Django

Final thoughts on static files

Hosting static files

A Quick Overview of HTTPS and Custom Domain Names

Setting Up a Domain Through AWS Route 53 for a Django App

Some hints for those not using AWS services

Not using AWS services

Domain Handling with Zappa - WWW and Non-WWW Options

Custom Domain Names

Creating a Cloud Database and Connecting It to a Django App

A Detailed Walkthrough for Creating Your First RDS with AWS

Connecting a Django App to a PostgreSQL Database

An Introduction to Creating Django Models [with Examples]

Final thoughts on databases

Connecting a Database

A Primer on Securing Serverless Apps in AWS

Creating a Virtual Private Cloud in AWS for a Relational Database

Securing an AWS Virtual Private Cloud for Django Deployment

Get Ready for Production

Whether you are a solo developer working on your next startup idea or a team of folks working with Django, this course shows you the way to simplify your operations overhead while saving money.  The open source Zappa utility paves the way to migrate your Django application away from old-school servers and onto the AWS Lambda serverless platform.  It's almost like having your own private Infrastructure team!

No need to watch for OS security patches or tweak Apache settings -- just focus on delivering value to your users.  All this with minimal changes to your Django application.  Leverage the power of AWS to rapidly respond to spikes in user traffic, while saving money by only paying for the web requests actually needed.

For folks ready for serverless Django, this course covers:

* Which Django apps are best to migrate and how to prepare them
* Configuring a generic and portable development environment easily set up by new developers in minutes
* Deploying and updating your code to AWS Lambda
* Best practices in serving Django static files
* Leveraging AWS services to secure your site with HTTPS and your own custom domain name
* Learning how to configure a secure network environment in AWS VPC
* Connecting your Django application to a hosted RDS database

All this while leveraging the AWS Free Tier.  While there are some lessons that may have additional cost to complete (e.g. bring your own domain name), the vast majority of this course will be using the AWS Free Tier and won't cost anything.

It's taught by Edgar Román. I was introduced to Django in 2009 and I consider it my go-to web framework. With continuous support from a vibrant community in addition to an incredibly rich ecosystem, I would be hard pressed to find another framework that matches up.

I've been using Zappa to host my Django applications for several years now, and I have found no other solution that is as powerful and cost-effective as serverless Django hosting on AWS -- especially for the solo developer working to get a product to market.

I hope you enjoy this course and harness the power of serverless Django with Zappa in your projects!

Learn how to migrate your Django application to a serverless environment hosted by AWS Lambda.

Serverless Django with Zappa

How to migrate your Django project to the AWS serverless environment

Adapt your code to changes necessary for running in the cloud

How to setup a reliable and consistent local development environment for serverless projects

How to setup and connect to a hosted RDS database

Learn about setting AWS IAM permissions for serverless projects

How to map a custom domain name to your Django project

Effectively serve Django static files via S3 or AWS Lambda

How to navigate the AWS Console to host multiple domain names

Learn about setting up a secure network environment using AWS VPC

has some strategies for deploying static files

 but in AWS Lambda, we have very different considerations. There are two common options.

Option 1 - serve static files from your Zappa project

You can configure your app to serve static files using the package 

. This enables your Django application not only to execute your Django views, but also deliver these static files when requested. This is normally not done by Django, because the web server (like Apache or NGINX) does this job. But since there is no web server we can configure, this package was created.

The advantages of this option are that your app has fewer dependencies. It doesn't rely on other AWS services or tools. It's also nice since usually your static files are tightly coupled with your application.

Additionally, WhiteNoise does a good job of compressing files before sending them to the web client. This speeds up the delivery of important assets and makes the web pages render faster.

The big downside of this approach is that you will be charged by AWS for using Lambda CPU cycles to serve up files that could be delivered much cheaper. For example, if you take a million downloads of your CSS file, an AWS S3 service can do that much cheaper than AWS Lambda.

---
title: Two Ways to Handle Django Static Files
description: A brief overview of two solutions
privateVideoUrl: https://fullstack.wistia.com/medias/m29ffht1g1
isPublicLesson: false
---

The Django project [has some strategies for deploying static files](https://docs.djangoproject.com/en/3.1/howto/static-files/deployment/) but in AWS Lambda, we have very different considerations. There are two common options.

## Option 1 - serve static files from your Zappa project

You can configure your app to serve static files using the package [WhiteNoise](https://docs.djangoproject.com/en/3.1/howto/static-files/deployment/). This enables your Django application not only to execute your Django views, but also deliver these static files when requested. This is normally not done by Django, because the web server (like Apache or NGINX) does this job. But since there is no web server we can configure, this package was created.

The advantages of this option are that your app has fewer dependencies. It doesn't rely on other AWS services or tools. It's also nice since usually your static files are tightly coupled with your application.

Additionally, WhiteNoise does a good job of compressing files before sending them to the web client. This speeds up the delivery of important assets and makes the web pages render faster.