Creating a CI/CD Jenkins Pipeline with GitHub Webhook that runs automatically the Production Stage via Amazon ECS- Fargate, and Amazon ECR.

In this article, we will create a CI/CD (continuous integration/continuous delivery and deployment) production pipeline, using Jenkins as a CI/CD automation software, Amazon ECS(Elastic Container Service)-Fargate as a container orchestration service, Amazon ECR(Elastic Container Registry) as an image (artifact) repository, Docker as an image builder, GitHub as a source code management. We will use the private GitHub repository with a “GitHub Personal Access Token” in the Jenkins pipeline, and use a GitHub Webhook to auto-trigger the Jenkins pipeline.
When running the pipeline, we’ll use the Nodejs application as an artifact. We will do it all step by step.

Topics we will cover:

1. Preparing a necessary environment.

2. Creating a GitHub Webhook to auto-trigger the pipeline

3. Creating role: “ecsTaskExecutionRole” for ECS

4. Deploying image to the ECS cluster

4. a. Creating an ECS cluster

4. b. Creating a task definition file

4. c. Registering the task definition file

4. d. Create a service

5. Preparing and explaining a Jenkinsfile of the pipeline

6. Preparing a Jenkins pipeline

7. Seeing that the pipeline is triggered automatically with the webhook when the code of the application changes

8. Clean up

9. As a result

10. Next post

11. References

If you like this article, I will be happy if you click on the Medium Following button to encourage me to write…