Introduction Here we are at the end of our long journey in the cloud which led us to implement our serveless system in synchronous and asynchronous mode. Our application meets the basic functional requirements to be used in production, however we cannot release a digital system without worrying about security. Security allows us to retain our customers, to assure them of the protection and anonymity of their data which passes through our application.

Introduction In our previous article, we focused on the lambda-Sync part of our serverless system which corresponds to the synchronous part of our application. We had already set up our entire continuous integration pipeline consisting of Github for the VCS, Codebuild to build our docker images and finally Cloudformation to deploy our resources in the AWS environment. For this second part, there is no need to reinvent the wheel. We will use the instruments already in place and implement our asynchronous circuit.

Introduction In my journey in the cloud and in the preparation of cloud certifications, I have been inspired by the AWS workshops carried out and generously made available to everyone by the AWS team. This workshop which deals with the implementation of a serverless system is a must for all aspiring cloud engineers. It covers both the event-driven approach and the synchronous web-server mechanism. In this post, we are working to resume the basic concept but bringing a DevOps concept with a pipeline to automate our deployments and also adding a front-end part also deployed in an automated way in the cloud.