AWS Builder Center
End-to-End DevOps CI/CD and GitOps Automation on AWS EKS

End-to-End DevOps CI/CD and GitOps Automation on AWS EKS

A hands-on DevOps implementation using Jenkins, SonarQube, Docker, Trivy, GitOps, Argo CD, Kubernetes, and Amazon EKS to automate application delivery from GitHub commit to Kubernetes deployment.

Overview

I recently completed a hands-on DevOps CI/CD and GitOps implementation on Amazon EKS, integrating Jenkins, Maven, SonarQube, Docker, Trivy, Docker Hub, GitOps, Argo CD, and Kubernetes.
The objective was to build an automated application delivery workflow from a developer code push through continuous integration, code-quality validation, container security, and GitOps-based deployment to Kubernetes.

Architecture

The architecture below represents the complete workflow implemented in this project.
Developer → GitHub → Jenkins → SonarQube → Docker & Trivy → Docker Hub → GitOps Repository → Argo CD → Amazon EKS → Kubernetes → LoadBalancer
[Insert the architecture diagram here]

CI/CD Workflow

A developer pushes application code to GitHub, which automatically triggers Jenkins.
Jenkins performs:
  • Source code checkout
  • Maven build and unit testing
  • SonarQube static code analysis
  • Quality Gate validation
  • Maven packaging
  • Docker image build
  • Trivy container vulnerability scanning
  • Docker Hub image push
  • GitOps repository checkout
  • Kubernetes deployment manifest update
  • Git commit and push
Docker images are tagged using the Jenkins build number, providing version traceability between the CI build and deployed application.

GitOps & Argo CD

A key design decision in this implementation was to keep CI and CD separated.
Jenkins does not directly deploy the application to Amazon EKS.
Instead, Jenkins updates the Kubernetes deployment manifest in the GitOps repository with the new Docker image version.
For example:
 projectimage:1  →  projectimage:2 
After the GitOps repository is updated, Argo CD detects the change and automatically synchronizes the desired state to the EKS cluster.
This follows the GitOps model where Git acts as the source of truth for Kubernetes deployment configuration.

Amazon EKS & Kubernetes

I manually created and configured an Amazon EKS cluster named  somesh  with 4 worker nodes.
The application runs as a Kubernetes Deployment with:
  • 3 application replicas
  • RollingUpdate strategy
  •  maxUnavailable: 1 
  •  maxSurge: 1 
The application is exposed using a Kubernetes LoadBalancer Service on port 8080.
The 4 EKS worker nodes provide the cluster capacity, while Kubernetes manages and schedules the 3 application pod replicas.

DevSecOps

Security and code quality are integrated directly into the CI pipeline.
SonarQube performs static code analysis and validates the configured Quality Gate.
Trivy scans the Docker image for vulnerabilities before it is pushed to Docker Hub. The pipeline is configured to fail when CRITICAL vulnerabilities are detected.
Jenkins Credentials are used for authentication instead of placing credentials directly in the pipeline.

Infrastructure & Platform Management

As part of this implementation, I manually configured and managed:
  • Jenkins Server
  • Jenkins Node-1
  • GitHub integration
  • Maven
  • SonarQube and Quality Gate
  • SonarQube webhook
  • Docker and Trivy
  • Docker Hub integration
  • Amazon EKS
  • Kubernetes resources
  • Argo CD
  • GitOps repository integration
After the initial infrastructure and platform setup, the application delivery workflow becomes automated.

End-to-End Result

The final workflow is:
GitHub Push → Jenkins CI → Quality & Security Validation → Docker Image → GitOps Update → Argo CD Auto Sync → Amazon EKS → Kubernetes RollingUpdate → Application
This implementation provided practical hands-on experience with CI/CD, GitOps, Kubernetes, Amazon EKS, containerization, DevSecOps, automated deployments, and continuous delivery.

Key Takeaway

The main focus of this project was not simply using individual DevOps tools, but understanding how they work together as a complete delivery platform.
Jenkins handles CI, Git acts as the deployment source of truth, Argo CD handles GitOps-based CD, and Kubernetes on Amazon EKS runs the application workload.

Project Repository

Any opinions in this article are those of the individual author and may not reflect the opinions of AWS.
Enjoyed reading this content? Let the author know!

Your likes, comments, shares, and saves help creators reach more builders.

Loading recommendations

Loading article