Tanuj Joshi

Cloud & DevOps engineer. I spend my time making infrastructure less painful — automating the boring parts, containerising the rest, and writing about what I learn along the way.

Currently

Exploring cloud-native observability, BGP routing, and self-hosting everything I can on my homelab.

AWS·Docker·Kubernetes·Terraform·CI/CD·GitHub Actions·Linux·Next.js·TypeScript·NGINX·Node.js·NixOS·
AWS·Docker·Kubernetes·Terraform·CI/CD·GitHub Actions·Linux·Next.js·TypeScript·NGINX·Node.js·NixOS·
scroll

Building things that actually run in production.

Ahmedabad, IndiaCloud EngineerSelf-hoster

I got into cloud engineering because I wanted to understand what happens after you push code. Turns out — a lot. And most of it can be automated.

My focus is production-grade infrastructure: Terraform for provisioning, Docker and Kubernetes for workloads, GitHub Actions for CI/CD. I care about making deployments boring — repeatable, observable, and easy to roll back.

Outside of work I run a homelab on a Raspberry Pi with a Tailscale mesh, self-host my own services, and occasionally write about what I'm tinkering with.

Notes & posts

Zero-downtime deployments with GitHub Actions and EC2

How I wired up a rolling-update pipeline that deploys Docker containers to EC2 without a single dropped request.

GitHub ActionsDockerEC2
Jul 2025

Kubernetes on Raspberry Pi — a practical guide

Setting up a bare-metal K3s cluster on Raspberry Pis, from flashing the OS to running real workloads with Helm.

KubernetesLinuxHomelab
May 2025

Why I containerise everything — even on a Pi

The case for Docker even on single-board computers, and how I keep the whole stack reproducible with Compose.

DockerDevOps
Mar 2025

Terraform state management without blowing up prod

Remote state, locking, workspaces, and the habits that keep infrastructure-as-code from becoming infrastructure-as-chaos.

TerraformAWS
Jan 2025

Technical stack

Cloud & Infrastructure

where I spend most of my time

AWSTerraformNGINXLinux

DevOps & Automation

the stuff that makes shipping pleasant

DockerKubernetesGitHub ActionsCI/CD

Development

enough to build and not break things

Next.jsTypeScriptTailwind CSSNode.js

My home infrastructure

A self-hosted stack running on a Raspberry Pi behind a Tailscale mesh. All containers managed with Docker Compose, exposed through NGINX.

Tailscale mesh (VPN)

Raspberry Pi (host)

Docker — bridge network

  • open-webui :3069 → 8080

Docker — host network

  • nexterm (host ports)
  • portfolio - next.js :3000

Host services (non-Docker)

  • nginx reverse proxy :80
  • postgres :5432 (localhost only)
  • sshd :22
  • unidentified node process :7800 / :6989

Internet

via NGINX :80

Home LAN

local network

AWS

Cloud infra & storage

GitHub Actions

CI/CD pipelines

Tailscale

Mesh VPN

NGINX

Reverse proxy

Docker

Container runtime

Postgres

Primary database

What I use

The tools, hardware, and software I use to build, deploy, and run things day-to-day.

Cloud & Infrastructure

  • AWS (EC2, ECR, S3, IAM)primary cloud platform
  • Terraforminfrastructure as code
  • NGINXreverse proxy
  • Linux (Ubuntu, Raspberry Pi OS)everywhere

DevOps & Automation

  • Docker & Docker Composecontainer runtime
  • Kubernetes / K3sorchestration
  • GitHub ActionsCI/CD pipelines
  • Tailscalemesh VPN

Homelab Hardware

  • Raspberry Pi 4Bprimary home server
  • Home LANlocal network
  • Tailscale meshremote access

Development

  • VS Code / Kiroeditor
  • Next.js + TypeScriptfrontend
  • Node.jsbackend scripts
  • Postgresprimary database

Self-hosted Services

  • Open WebUI + Ollamalocal AI chat
  • Nextermweb terminal
  • Portainer (optional)container management

Monitoring & Ops

  • GitHub Actions logsdeployment visibility
  • NGINX access logstraffic monitoring
  • SSHremote management

Let's build something

Always happy to talk about cloud infrastructure, DevOps challenges, or a good engineering problem. No pitch decks needed.

Usually replies within a day.