CLOUD & NETWORK ENGINEERING · OPEN TO WORK

Ravi Kumar builds
networks that heal themselves.

Cloud & Network Engineer · AWS in Terraform, Linux under systemd, DNS and VPNs I run for real. Everything on this site is measured on the machine it describes.

CompTIA Security+ Network+ Linux Essentials A+ ITIL 4 B.S. Cloud & Network Eng (AWS) · WGU
See what I run → AWS + network labs
  • 229scheduled jobs in the fleet
  • 11AWS + networking labs
  • 3sites through Cloudflare Tunnel
  • 6certifications

Pittsburg, CA · San Francisco Bay Area · remote

topology — live packets, real nodes
Pi fleet Cloudflare edge · tunnels AWS lab county network · operator

$ whoami

Network and systems engineer moving into cloud engineering. By day I support a county public-works network: DNS, DHCP, Active Directory, Palo Alto GlobalProtect VPN, Cisco switching in the IDFs, and Microsoft Intune device management. On my own time I run a production Linux fleet that serves real users and real payments, and I build AWS infrastructure in Terraform with a runner that proves each lab works and tears it down. I like systems that explain themselves: everything I run logs, alerts, and heals.

Looking for: Cloud Engineer I / Associate, Cloud Infrastructure Engineer, Cloud Support Engineer, or a Network Engineer role with a cloud track. AWS first; comfortable learning Azure/GCP.

$ ls # where to look

⚙ production/

The Raspberry Pi 5 I operate as a small production environment: 229 timers, zero inbound ports, paging on failure, a self-heal loop and a watchdog that checks the healers. Plus two shipped products that take real traffic and real payments.

status board, edge architecture, products →

▲ labs/

AWS in Terraform with a runner that applies, exercises the live API, destroys, and writes an evidence report. The flagship is a container service deployed by GitHub Actions through OIDC, with an approval gate and a smoke test that can fail.

7 AWS labs, 5 networking labs, what's next →

history experience/

County public-works network today; Meta, Apple and Bay Alarm before that. Six certifications, a B.S. in Cloud & Network Engineering in progress, and the exact skills behind each line.

timeline, skills, certs, résumé →

$ git log --since=2026-09-25 # recent, dated

  1. Lab 07 green on real AWS: EKS cluster, Helm-deployed app with HPA and PDB, kube-prometheus-stack; smoke test fired the 5xx alert on purpose and watched it go red. labs
  2. Lab 06 pipeline green end to end on real AWS: lint → validate → build+push (OIDC) → plan → approval → apply → smoke, then destroyed with zero survivors. the run
  3. Labs 01, 03, 04 and 05 re-run through the runner with evidence captured; two runner bugs fixed on the way (lab path precedence, ECS task ENI timing). aws-labs
  4. aws-ops-toolkit published: six boto3 operations tools with 65 offline tests (moto) and a CI run that never touches a real account. aws-ops-toolkit
  5. fleet-ops published: the systemd patterns, alerting pipeline and five postmortems from the production fleet, scrubbed of hostnames and account ids. fleet-ops
  6. PaperReel live for $0: landing on Cloudflare Pages, API through a Tunnel on the Pi, Stripe Checkout, per-service spend caps. products

$ ./contact.sh

Hiring for an entry-level cloud or network role in the Bay Area or remote? The short version is one page.

résumé.pdf ↗ contact →