Adding Lambda Authorizers to your Serverless Applications

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.

My Newest Free Course - Serverless for Frontend Developers

My Newest Free Course - Serverless for Frontend Developers

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

The best part? It’s 100% free! Feel free to check it out here. Let me know what you think on Twitter!

Updating Route 53 Domains with awsmailman

One of my few possessions is an abundance of poorly-chosen Amazon Route 53 domain names with outdated contact addresses from moving between overpriced apartments - I am what you might call a tech typical millennial.

So I wrote a Python package called awsmailman to help do this for me and now you can use it too.

Announcing Stormlight Consulting

Announcing Stormlight Consulting

I’ve launched a website for Stormlight Consulting. You can now take a look at different consulting services I offer and get in touch with me for initial consultations. If you’d like to learn more, check out the Stormlight Consulting Website!
AWS First-In-First-Out Queues

Recently, I needed to put together system that would take new DynamoDB table items, queue up JSON messages in first-in-first-out order, and trickle them out to a 3rd party API over time.

I love not having to maintain things later so I decided to throw together a solution on top of managed AWS services. Here’s a high-level diagram of what I came up with:

Full Queue Diagram

Let’s take a look at how it all works.