It starts with the developer pushing new code to the main branch of its version control system (in our case, it's GitHub). As soon as the new code is pushed, the Jenkins GitHub plugin detects the change as per its defined job, and triggers the Jenkins job to deploy the new code to its infrastructure. Jenkins then communicates with Code Deploy to trigger the code to the Amazon EC2 machine. Since we need to make sure that our deployment is successful, we can set up a notification section, which will notify us of the status of deployment so that it can reverted back if needed.