Integrating DevOps Tools into a CI/CD Pipeline in AWS

During this course, we will focus on building a secure CI/CD pipeline, by integrating some well-known DevOps tools. In a typical production scenario, developers working on the same application push their new features to a common repository, which is represented most of the times by Git. In the next step, there comes the need of a continuous integration & building tool, such as Jenkins, whose job is to periodically perform polling activities to the Git repository, and when it senses there was a new commit, it takes the new application, performs some quality and security analysis of the code through the SonarQube app, then builds it with the help of Maven plugin and sends the build artifacts to Ansible. Ansible packages these artifacts into Docker containers and deploys them on the production servers, so that the application is accessible for the clients. All this process happens automatically, meaning that after developers push their new code to Git, the features should be seen by the end user without any intervention from the Dev or Ops teams. The whole infrastructure that performs this process is hosted in AWS cloud and created with the help of the most popular infrastructure provisioning tool, Terraform. Each independent server (Jenkins, Ansible, SonarQube & Application hosts) will also be monitored by Grafana, and alerts will be configured in the case of any malfunctions.