In the previous phase, we successfully set up Continuous Integration (CI) using Jenkins to automate the build and testing stages of our application. Now, we take the pipeline forward — by incorporating Docker to containerize our application artifacts, pushing the images to Amazon ECR, and finally implementing Continuous Deployment (CD) by hosting those images via AWS ECS.
This write-up builds directly on the earlier Jenkins CI pipeline and details how that workflow was extended into a full CI/CD pipeline with Docker and AWS.

We began by integrating Docker into the CI workflow to containerize the application. This allowed the application, along with its environment and dependencies, to be packaged into a portable and consistent format.
Other registries like Docker Hub, Google Container Registry, or Azure Container Registry could have been used, but AWS ECR was chosen for its seamless integration with other AWS services.
AmazonEC2ContainerRegistryFullAccessAmazonECS_FullAccess for deploymentInstalled relevant plugins:
Stored AWS credentials securely within Jenkins
Installed Docker Engine on the Jenkins host
Verified Docker installation and permissions by:
jenkins user to the docker group
docker imagesThe Jenkins job successfully:
Dockerfile from the application repo