Yes. This is clickbait. But I mean it!

I’ve spent weeks trying to configure ECS clusters, debugging Fargate, spinning up and debugging EKS cluster permissions, and even trying to deploy containers on EC2 instances and hopefully never will again!

Fortunately, AWS has an option that actually implements the full “serverless” ethos and doesn’t make me dig into as many of the dirty details as I’ve had to before: AWS App Runner. In this post I’ll show you how to throw together a simple AWS App Runner API that will help you get around any of the AWS Lambda limitations. I’ll do this with Node.js but you can easily use other languages.

I have some exciting news: I’m writing a book on serverless development!

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!

Yesterday, I wrote a post on creating a Cognito Authorizer for an AWS HTTP API. But I didn’t do much with the Lambda functions themselves! In this post, I’ll expand the previous post and show you how to get an entire user profile service up and running with the same architecture using Python or Node.js. Let’s get started!

This is the 8th project in my Twenty Projects in Twenty Days series! In this project, we’ll look at how to use Amazon Translate with Python using Boto3 and with Node.js using the AWS SDK for JavaScript. We’ll translate our first text in under 10 lines of code so let’s get started! You can copy the code from the GitHub repo here.