sls-mentor VS learn-serverless-dev-to

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. 😉

This lambda reacts to an EventBridge event. It has access to the detail of the event, which is a Reservation object. It uses this data to hydrate the SES template and send an email to the restaurant owner. It also uses an API_URL environment variable to create the link to confirm the reservation. (The creation of the link is done inside the template, check it here)

I plan to continue this series of articles on a bi-monthly basis. I already covered the creation of simple lambda functions and REST APIs, as well as interacting with DynamoDB databases. You can follow this progress on my repository! I will cover new topics like file storage, creating event-driven applications, and more. If you have any suggestions, do not hesitate to contact me!

In this article, I will start from the project I created in the last article. If you want to follow along, you can clone the repository and continue from the introduction branch. If you want to start from scratch, you can use the CDK to create a new project, by following the instructions of the last episode.

Do not hesitate to ask for help if you get stuck! I will be happy to help you! You can also check this repository on my github to see the solution, and the previous two Lambda functions we created together.