DevOps & Cloud Engineering

Build. Ship.
Beyond
the ordinary.

Hey, I'm Lovish Barber. An aspiring DevOps & Cloud Engineer pursuing an MCA in Cloud Computing. I build AWS infrastructure, automate delivery, and explore reliable systems.

Explore my projects ↗GitHub ↗
Infrastructure as code. Learning by building.
  CLOUD TOPOLOGYINTERACTIVE / 3D
CONNECTED BY DESIGNOne ecosystem.
Infinite possibilities.
DRAG TO ORBIT · SELECT TO EXPLORE
MY EVERYDAY TOOLKITaws⌣◈ Terraform▦ Docker⎈ Kubernetes⌘ Jenkins◉ Grafana
01 / SELECTED WORK

Built to learn. Built to work.

Hands-on projects across the cloud-native lifecycle.

All repositories ↗

Showing 7 projects

02 / THE DELIVERY LIFECYCLE

More than a deploy button.

How the pieces of my projects connect—from infrastructure to insight.

◇
01 / PROVISION

Define the foundation.

Express infrastructure in Terraform. Bring EC2, networking, and EKS configuration into version control instead of relying on manual setup.

</>
02 / BUILD & CHECK

Make delivery repeatable.

Connect code to Jenkins or GitHub Actions. Package applications with Docker and integrate tests or security checks into the workflow.

⎈
03 / DEPLOY

Describe the desired state.

Use Kubernetes manifests and Helm to define workloads. Explore GitOps with Argo CD to connect repository changes to cluster deployments.

◉
04 / OBSERVE

Understand what is running.

Collect metrics with Prometheus, explore them with PromQL, and use Grafana to see how pods consume CPU and memory.

03 / UNDER THE HOOD

The thinking behind the builds.

A closer look at three documented projects.

ARCHITECTURE → IMPLEMENTATION
01 / INFRASTRUCTURE AUTOMATION

From a repository
to an EKS cluster.

This project brings infrastructure provisioning and application deployment into one documented workflow. Jenkins runs on EC2, while Terraform defines the AWS resources.

  • Provision EC2, VPC, and EKS infrastructure with Terraform.
  • Use an S3 bucket for Terraform state storage.
  • Run Terraform stages through Jenkins pipelines.
  • Deploy a sample NGINX workload with Kubernetes manifests.
Read the setup & troubleshooting notes ↗
TOPOLOGY / INFRASTRUCTURE PIPELINE
GitHubTerraform code
→
JenkinsHosted on EC2
↓
TerraformProvision AWS resources
↓
Amazon EKSKubernetes cluster
→
NGINXSample workload
Simplified architecture · not live infrastructure
02 / OBSERVABILITY & GITOPS

A deployment is only
part of the story.

The observability project connects container delivery to cluster-level visibility. A static site becomes a practical way to explore GitOps and resource metrics.

  • Build a Docker image and publish it to Docker Hub.
  • Deploy Kubernetes manifests through Argo CD.
  • Install kube-prometheus-stack with Helm.
  • Query CPU and memory usage and visualize the results.
Explore the dashboards & PromQL examples ↗
TOPOLOGY / DEPLOYMENT & VISIBILITY
Argo CDGitOps sync
→
KubernetesContainer workload
↓
PrometheusCollect & query metrics
↓
GrafanaCPU & memory dashboards
Simplified architecture · not live monitoring
03 / SECURITY IN DELIVERY

Build the checks
into the workflow.

The DevSecOps project explores how code quality, dependency analysis, and image scanning can fit into a Jenkins-led delivery pipeline.

  • Analyze code quality with SonarQube.
  • Check dependencies with OWASP Dependency-Check.
  • Scan container images with Trivy and Docker Scout.
  • Use Helm and Argo CD for Kubernetes delivery.
Inspect the pipeline & project documentation ↗
TOPOLOGY / SECURITY CHECKPOINTS
JenkinsPipeline orchestration
↓
SonarQubeCode quality
OWASPDependencies
↓
Trivy / ScoutContainer scanning
→
Argo CDDelivery
Conceptual flow · see repository for implementation
The code is part of the story. The documentation is the rest.

Explore repository READMEs for setup steps, architecture diagrams, and screenshots.

Browse GitHub ↗
04 / BEHIND THE TERMINAL

Curiosity drives me.
Automation moves me.

I'm Lovish, an aspiring DevOps & Cloud Engineer pursuing a Master of Computer Application in Cloud Computing at Parul University. My projects connect the pieces of modern software delivery—from provisioning AWS infrastructure to deploying containers and understanding their behavior.

A background in cybersecurity gives me another perspective on cloud engineering: understanding access, investigating issues, and keeping security in the delivery process. I’m continually exploring DevOps tools and turning hands-on experiments into repeatable workflows.

Follow my learning journey ↗
01

Cloud & infrastructure

AWS · EC2 · EKS · S3 · Lambda · Terraform

02

Containers & delivery

Docker · Kubernetes · Helm · Jenkins · GitHub Actions · Argo CD

03

Security & observability

SonarQube · Trivy · Prometheus · Grafana · PromQL

04

Scripting & version control

Linux · Bash · Ansible · Git · GitHub

05 / THE TOOLKIT

The right tools. Connected.

Technologies explored through my projects and ongoing learning.

Cloud foundations

Compute, storage, and managed services for cloud-hosted applications.

AWSEC2EKSS3CloudFront

Infrastructure as code

Versioned infrastructure definitions and repeatable provisioning workflows.

TerraformVPCS3 state

Containers & orchestration

Package applications and define how workloads run in a cluster.

DockerKubernetesHelm

Delivery & GitOps

Move from source changes to automated builds and declared deployments.

JenkinsGitHub ActionsArgo CDGit

Security & code quality

Explore checks for application code, dependencies, and container images.

SonarQubeOWASPTrivyDocker Scout

Metrics & serverless

Observe workloads and explore event-driven application backends.

PrometheusGrafanaPromQLLambdaDynamoDB
06 / MY JOURNEY

A foundation in security.
A focus on the cloud.

Education and hands-on experience behind the projects.

01 / EDUCATION

Master of Computer Application

Cloud Computing · Parul University

Vadodara, Gujarat

IN PROGRESS · EXPECTED 2027

Bachelor of Computer Application

Mohanlal Sukhadia University

Udaipur

UNDERGRADUATE EDUCATION

02 / EXPERIENCE

Cybersecurity Internship

Account recovery, security investigations, and networking support.

  • Recovered compromised accounts using security tools and protocols.
  • Investigated fraud and identity theft cases.
  • Used ethical hacking, encryption, and networking tools to support security work.
  • Configured and troubleshot network devices and cabling.
SECURITY · INVESTIGATION · NETWORKING
07 / CERTIFICATIONS & TRAINING

Strengthening the foundations.

Cloud architecture, security, and networking knowledge.

Public Credly profile ↗
AWS Certified Solutions Architect – Associate badgeAMAZON WEB SERVICES

AWS Certified Solutions Architect – Associate

Expires 30 Jan 2028

View on Credly ↗
AWS Educate Getting Started with Networking badgeAWS EDUCATE · TRAINING BADGE

AWS Educate Getting Started with Networking

Issued 11 Mar 2025

View on Credly ↗
ADDITIONAL COURSEWORK
Network+ Training · Udemy

Networking coursework, separate from a CompTIA-issued certification.

08 / ALWAYS ITERATING

Building is how I learn.

Projects, documentation, and the next question to explore.

~/lovish/learning-notes

“Build it to understand it.
Document it to make
the learning reusable.”

My GitHub is a working collection of cloud and DevOps experiments—not just finished application screens. The infrastructure, pipelines, and setup notes are part of the work.

See what I'm building ↗

  1. Connect the whole delivery lifecycle

    Explore how infrastructure, CI/CD, containers, and observability fit together rather than treating each tool as an isolated topic.

  2. Keep configuration close to the code

    Work with Terraform definitions, Kubernetes manifests, Helm charts, and pipeline configuration stored in repositories.

  3. Make the work inspectable

    Share architecture diagrams, setup instructions, screenshots, and troubleshooting notes in project documentation.

  4. Continue the cloud-todo project

    The team project's README records the API, unit tests, Dockerfile, and pipeline configuration. DynamoDB integration remains a planned next step.

09 / START A CONVERSATION

Great things start
with a simple hello.

Have an opportunity, a project, or a cloud problem to talk about?

Let's talk ↗