I recently wrote a guide on using Serverless CI/CD Preview Deployments. You can use this feature to create your own preview deployments of feature branches when integrating with GitHub.
So you’ve developed a snazzy new Serverless API on AWS and everything is going great. That is until you realize that there might eventually be production data behind it that you don’t want someone with Postman and 20 minutes on their hands to have access to. That’s where Lambda Authorizers come in. They’re a way to make sure that your API will only respond to authorized callers. Let’s look at how to implement authorizers for ourselves using an example application called Serverless Jams - where we vote on our favorite coding-related music.
I have a new three-hour long course on building serverless applications from the perspective of a frontend developer. Some of the things you’ll learn include:
- How to deploy serverless frontends on AWS with SSL, a custom domain, and the CloudFront CDN
- How to spin up your first backend APIs with the Serverless Framework
- How to integrate Auth0 into your frontend
- How to use Auth0 to secure your backend APIs