Complete Guide to Jenkins CI/CD Pipeline Setup on AWS EC2 (Ubuntu)

Developers from the Application team write the code and push it to GitHub . Now, instead of manually building and deploying the application, we use Jenkins as a CI/CD tool to automate the entire process. Here’s how the flow works: Developers commit and push the code to GitHub . Jenkins is connected to the repository using a webhook. Whenever new code is pushed, Jenkins automatically triggers a pipeline. Jenkins pulls the latest code and starts the build process . During the build stage, Docker is used to create a Docker image from that code. The Docker image is then pushed to a container registry (like Docker Hub or ECR). In the deployment stage, Jenkins deploys that image either: On an Amazon EC2 instance, or On a Kubernetes cluster. Once the application is live, monitoring tools like Prometheus are used to monitor application health, metrics, and performance. In Simple Terms Jenkins acts as the brain of the CI/CD pipeline. It automates: Code integration (Continuous Integration) Testi