Imagine you’re writing a serverless API using AWS Lambda and API Gateway. If you want to accept JSON payloads from POST requests that contain data created by your frontend client you may end up needing to validate that data to make sure it conforms to your expectations before you process it. Let’s look at a simple way of doing this with API Gateway’s JSON Schema validation.

This is project 15 in my Twenty Projects in Twenty Days series! This time, we’re looking at how to create an AWS HTTP API with Python. This will be the Python version of yesterday’s project where we created a Surveys service API to track three entities - customers, customer surveys, and survey responses. Let’s get started!

As project fourteen of my Twenty Projects in Twenty Days series I’ll show you how to create an AWS HTTP API with Node.js. We’ll design it around the same serverless survey service that I’ve previously shown using Express.js and using Flask. It’ll be used to track three entities - customers, customer surveys, and survey responses. Let’s get started!

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.

During AWS re:Invent this year AWS announced a new way to make HTTP APIs with API Gateway v2. It now includes things like native support for JSON Web Tokens (JWTs) and a vastly simplified number of AWS resources to get an API up and running. You can read about all the updates here in my post on the Serverless Blog.