serverless-esbuild VS sls-mentor

Support Yarn PnP with externals bundling #327

We use serverless-esbuild to transpile our TypeScript code to JavaScript.

You should use appropriate tools to bundle your Lambda functions with a minimal size. For example, the Serverless Framework, with the serverless-esbuild plugin, automatically bundles your code and uploads it to AWS.

One of the most important aspects of serverless development is keeping an eye on your bundle sizes and to reduce cold start times on Lambda. Keeping this in mind, the template utilizes serverless-esbuild and serverless-analyze-bundle-plugin to provide function analysis out-of-the-box. I opted for serverless-esbuild over serverless-bundle for a few reasons:

Its faster and easier to setup that webpack and drastically reduces the size of the archive. For Serverless framework users there is https://github.com/floydspace/serverless-esbuild and if you use SAM CLI, you already get this for free since they now use esbuild in the build process

if you can, try using https://github.com/floydspace/serverless-esbuild - esbuild is stupid fast and it produces tiny artifacts. Its dead simple too compared to the webpacks/rollups/etc.

This compilation is based on 🛡 sls-mentor 🛡, my free open-source tool that automatically checks 30 serverless best practices on your AWS serverless projects (no matter the framework). Feel free to check it out!

I recently packaged my awesome, open-source, AWS stack auditing tool SLS-mentor into a github action. On this occasion, I was confronted with the question of reproducibly configuring AWS authentication on a remote CI/CD job. In this article, I will explain to you how to proceed.

It is considered best-practice to use failure destinations on all your asynchronous Lambda functions (for data retention and notification purposes). Remember sls-mentor? It automatically checks that you use failure destinations on all your asynchronous Lambda functions, so that you know where to put your efforts first.

Find sls-mentor on Github ⭐️

With my team we have been building sls-mentor, a free and open source tool to audit your serverless stack on AWSand to give you tips to improve it!

We've got existing issues waiting for contributors, and we are open to new ideas too! Feel free to join us on GitHub!

It is basically a big cloud linter, feel free to check it out to learn more about AWS!

Introducing sls-mentor: a new open-source tool allowing you to audit your AWS serverless infrastructure. Like linters, it is based on rules, and it implements a rule verifying that all your S3 Buckets have "Block public access" enabled.

But a problem persists: how do I simply now which Lambda functions are using these deprecated runtimes? This is where sls-mentor comes in. It is a CLI tool that allows you to audit your AWS serverless infrastructure. It can be used to find deprecated runtimes on your Lambda functions.

As I dived in this topic, I added a security check to the audit tool that I use in my team: sls-mentor. This is an open source audit tool that helps us enforce best practices on our projects. Don’t hesitate to try it and send feedback to the team via a GitHub issue, the project is actively maintained. 😉