Not using AWS services
Some hints for those not using AWS services
Get the project source code below, and follow along with the lesson material.
Download Project Source CodeTo set up the project on your local machine, please follow the directions provided in the README.md file. If you run into any issues with running the project source code, then feel free to reach out to the author in the course's Discord channel.
This lesson preview is part of the Serverless Django with Zappa course and can be unlocked immediately with a \newline Pro subscription or a single-time purchase. Already have access to this course? Log in here.
Get unlimited access to Serverless Django with Zappa, plus 70+ \newline books, guides and courses with the \newline Pro subscription.
[00:00 - 00:11] Thus far in this module, we've tried to make it very easy for the students to get on board with a custom domain name. We've used Route 53 and Amazon Certificate Manager in order to do this.
[00:12 - 00:23] However, for whatever reason, some students may not be able to use these Amazon services to associate a custom domain name with their Zappa project. So, what do we do then?
[00:24 - 00:43] Well, you're going to have to work with your certificate authority or other organization that manages your SSL certificates. You're going to need a PEM encoded certificate, the PEM encoded unencrypted private key, and the PEM encoded certificate chain.
[00:44 - 00:52] That's a lot of jargon to throw at you. However, if you're working with an outside certificate authority, they should be able to provide these three files.
[00:53 - 01:12] Once you have these files, go ahead and add them to your Zappa settings.json file using the format shown here. Once that's done, then you can run the Zappa utility certified. Just type Zappa certified dev, and it will kick off the certified process just like we've seen in the previous lesson.
[01:13 - 01:19] Remember, this may take up to 40 minutes to associate the domain name with your Zappa project.