| Started | December 2025 |
| Target Completion | December 2026 |
| Total Projects | 69 |
| Infrastructure Cost | $0/month |
| Everything Public | ✅ Yes |
Duration: ~1.5 weeks | Platform: Laptop (WSL2)
| # | Project | Status | Repository |
|---|---|---|---|
| 0.1 | My Linux Lab: From Zero to Command Line | ✅ | p01-linux-lab |
| 0.2 | Bash Automation: 10 Scripts for Real Problems | ✅ | p02-bash-automation |
| 0.3 | WireGuard VPN Server on Google Cloud | ✅ | p03-wireguard-vpn |
| 0.4 | SSH Hardening & Bastion Host Pattern | ✅ | p04-ssh-hardening |
Duration: ~2.5 weeks | Platform: AWS Free Tier + LocalStack
| # | Project | Status | Repository |
|---|---|---|---|
| 1.1 | Static Website: CDN + Custom Domain + SSL | ✅ | p1.1-static-site-cdn |
| 1.2 | EC2 Web Server: Nginx + Node.js from Scratch | ✅ | p1.2-ec2-web-server |
| 1.3 | Three-Tier Architecture: Web + App + Database | ✅ | p1.3-three-tier-architecture |
| 1.4 | Serverless: Lambda + API Gateway + DynamoDB | ✅ | p1.4-serverless-api |
| 1.5 | Auto Scaling: Systems that Scale Themselves | ✅ | p1.5-auto-scaling |
| 1.6 | S3 Event-Driven: Image Processing Pipeline | ✅ | p1.6-s3-image-pipeline |
| 1.7 | SQS + SNS: Message Queue Architecture | ✅ | p1.7-message-queue |
| 1.8 | IAM Deep Dive: Least Privilege Permission Design | ✅ | p1.8-iam-deep-dive |
Duration: ~2 weeks | Platform: Laptop
| # | Project | Status | Repository |
|---|---|---|---|
| 2.1 | Dockerize 5 Different Application Types | ✅ | p2.1-docker-multi-app |
| 2.2 | Multi-Stage Build: 1GB → 87MB Images | ✅ | p2.2-docker-multistage-build |
| 2.3 | Docker Compose: Full Stack in One Command | ✅ | p2.3-docker-compose-fullstack |
| 2.4 | Container Registry: Push, Pull, Manage | ✅ | p2.4-container-registry |
| 2.5 | Docker Security Hardening | ✅ | p2.5-docker-security |
| 2.6 | Container Monitoring: cAdvisor + Prometheus + Grafana | ✅ | p2.6-container-monitoring |
| 2.7 | Docker Swarm: Multi-Node Orchestration | ✅ | p2.7-docker-swarm |
Duration: ~3 weeks | Platform: LocalStack + AWS Free Tier
| # | Project | Status | Repository |
|---|---|---|---|
| 3.1 | Terraform Fundamentals: Infrastructure as Code | ✅ | p3.1-terraform-fundamentals |
| 3.2 | Complete VPC from Scratch | ✅ | p3.2-terraform-vpc |
| 3.3 | Remote State: Team Collaboration Setup | ⏳ | — |
| 3.4 | Terraform Modules: Reusable Infrastructure Library | ⏳ | — |
| 3.5 | Multi-Environment: Dev, Staging, Production | ⏳ | — |
| 3.6 | Terraform CI/CD: Auto Plan and Apply | ✅ | p3.6-terraform-cicd |
| 3.7 | Terragrunt: DRY Infrastructure at Scale | ⏳ | — |
| 3.8 | Pulumi: IaC with TypeScript | ⏳ | — |
Duration: ~2 weeks | Platform: GitHub Actions (unlimited for public repos)
| # | Project | Status | Repository |
|---|---|---|---|
| 4.1 | GitHub Actions: Full CI Pipeline | ✅ | p4.1-github-actions-ci |
| 4.2 | Full CD Pipeline: Code to Production | ⏳ | — |
| 4.3 | Blue/Green Deployment: Zero Downtime | ⏳ | — |
| 4.4 | Canary Deployment: Gradual Traffic Shifting | ⏳ | — |
| 4.5 | GitOps with ArgoCD | ⏳ | — |
| 4.6 | Pipeline Security: SAST, DAST, Dependency Scanning | ⏳ | — |
| 4.7 | Self-Hosted GitHub Actions Runner | ⏳ | — |
| 4.8 | Semantic Release: Automated Versioning | ⏳ | — |
Duration: ~3.5 weeks | Platform: Minikube + kind (laptop)
| # | Project | Status | Repository |
|---|---|---|---|
| 5.1 | Kubernetes Fundamentals: All Core Concepts | ⏳ | — |
| 5.2 | Config & Secrets Management in Kubernetes | ⏳ | — |
| 5.3 | Persistent Storage: Stateful Apps in K8s | ⏳ | — |
| 5.4 | Ingress: Traffic Management + Automatic TLS | ⏳ | — |
| 5.5 | Autoscaling: HPA, VPA, and KEDA | ⏳ | — |
| 5.6 | Helm: Package Manager for Kubernetes | ⏳ | — |
| 5.7 | Production-Grade K8s Cluster: All Components | ⏳ | — |
| 5.8 | Multi-Tenant K8s: RBAC and Hard Isolation | ⏳ | — |
| 5.9 | Kubernetes Operator: Extend the K8s API | ⏳ | — |
Duration: ~2.5 weeks | Platform: Laptop (Docker Compose)
| # | Project | Status | Repository |
|---|---|---|---|
| 6.1 | Prometheus + Grafana: Full Observability Stack | ⏳ | — |
| 6.2 | OpenTelemetry: Instrument Your Own Application | ⏳ | — |
| 6.3 | Distributed Tracing Across 5 Services | ⏳ | — |
| 6.4 | Centralized Logging: Loki + Promtail + Grafana | ⏳ | — |
| 6.5 | Alerting That Actually Works | ⏳ | — |
| 6.6 | SLO/SLI: Measure What Actually Matters | ⏳ | — |
| 6.7 | FinOps: Cloud Cost Visibility Dashboard | ⏳ | — |
| 6.8 | Chaos Engineering: Intentionally Break Production | ⏳ | — |
Duration: ~2.5 weeks | Platform: AWS Free Tier + Laptop
| # | Project | Status | Repository |
|---|---|---|---|
| 7.1 | AWS Security Audit: Find Your Own Vulnerabilities | ⏳ | — |
| 7.2 | HashiCorp Vault: Centralized Secrets + Dynamic Credentials | ⏳ | — |
| 7.3 | Zero Trust Network: mTLS with Linkerd | ⏳ | — |
| 7.4 | WAF + DDoS Protection with Cloudflare | ⏳ | — |
| 7.5 | Policy as Code: Infrastructure Guardrails | ⏳ | — |
| 7.6 | Container Runtime Security: Real-Time Anomaly Detection | ⏳ | — |
| 7.7 | Incident Response Playbook: 5 Real Scenarios | ⏳ | — |
Duration: ~3 weeks | Platform: Laptop + Google Cloud + Cloudflare
| # | Project | Status | Repository |
|---|---|---|---|
| 8.1 | Microservices: Decompose a Monolith into 5 Services | ⏳ | — |
| 8.2 | Event-Driven Architecture: Kafka + CQRS + Event Sourcing | ⏳ | — |
| 8.3 | Service Mesh: Istio Traffic Management | ⏳ | — |
| 8.4 | Multi-Cloud: AWS + GCP + Cloudflare | ⏳ | — |
| 8.5 | Disaster Recovery: RTO Under 15 Minutes | ⏳ | — |
| 8.6 | Database Optimization: 10x Performance Without New Hardware | ⏳ | — |
| 8.7 | Real-Time Data Pipeline: Analytics Updated Every Second | ⏳ | — |
| 8.8 | Internal Developer Platform: Self-Service Infrastructure | ⏳ | — |
Duration: ~5 weeks | Platform: Everything built so far
| # | Project | Status | Repository |
|---|---|---|---|
| 9.1 | SaaS Infrastructure: Multi-Tenant Auto-Onboarding | ⏳ | — |
| 9.2 | FinOps: Full Cost Analysis of This Entire Journey | ⏳ | — |
| 9.3 | Performance Engineering: Benchmark to 1000 Concurrent Users | ⏳ | — |
| 9.4 | Platform Migration: On-Premise to Cloud | ⏳ | — |
| 9.5 | Security Operations: SIEM with Wazuh | ⏳ | — |
| 9.6 | MLOps: Infrastructure for Machine Learning | ⏳ | — |
| 9.7 | Homelab: ASUS TUF as a Mini Data Center | ⏳ | — |
| 9.8 | Open Source Contribution: Merged PR in a Real Project | ⏳ | — |
| 9.9 | Portfolio Documentation: GitHub + LinkedIn Complete | ⏳ | — |
| 9.10 | Capstone: Agenda Prestasi Infrastructure v2 | ⏳ | — |
From network infrastructure operations to cloud-native engineering — built in public, documented in detail, $0 infrastructure cost.
4+ years running FTTH networks → building SaaS on Cloudflare Workers → now going deep into cloud engineering the right way: by building everything from scratch.
I'm Aza — a network and infrastructure engineer from Indonesia transitioning into cloud engineering.
My background is operational: 4+ years managing FTTH internet infrastructure with MikroTik RouterOS, OLT/ONT equipment, and Linux servers in production environments where downtime has real consequences.
Now I'm going all-in: working through 70 structured cloud engineering projects to build deep, documented, and demonstrably real expertise. Everything is public. Every project has an architecture diagram. Every phase gets an honest write-up of what worked, what didn't, and what I learned.
Why 70 projects instead of certifications? Because when a recruiter asks "show me what you've built," I want to have 70 answers backed by public repositories.
Cloud Platforms AWS (EC2, Lambda, RDS, S3, VPC, IAM, DynamoDB, SQS, SNS, CloudFront) · Google Cloud · Cloudflare Workers/Pages/R2/Tunnel
Containerization & Orchestration Docker · Docker Compose · Docker Swarm · Kubernetes · k3s · Minikube · kind · Helm · ArgoCD · Kustomize
Infrastructure as Code Terraform · OpenTofu · Terragrunt · Pulumi (TypeScript)
CI/CD & Automation GitHub Actions · Semantic Release · Conventional Commits · GitOps · Blue/Green · Canary Deployments
Monitoring & Observability Prometheus · Grafana · Loki · Promtail · Alertmanager · Jaeger · OpenTelemetry · Chaos Mesh
Security HashiCorp Vault · OPA/Conftest · Falco · Trivy · Prowler · mTLS with Linkerd · WAF with Cloudflare
Databases & Storage PostgreSQL · Redis · DynamoDB · ClickHouse · MinIO · Supabase
Networking Linux Networking · WireGuard VPN · Nginx · Traefik · cert-manager · Let's Encrypt · Cloudflare Tunnel
Languages Bash · Python · TypeScript · Go (Kubernetes Operator)
Each completed project gets its own public repository following this naming convention:
p01-linux-lab
p02-bash-automation
p03-networking-deep-dive
p04-wireguard-vpn
...and so on
Every repository contains:
README.mdwith architecture diagram, problem statement, and tech stack- Working code or configuration files
- Lessons learned: what worked, what didn't, and why
- Links to the LinkedIn post documenting that project
Every project in this roadmap runs on $0/month of infrastructure:
- AWS Free Tier → EC2 t2.micro, Lambda (1M req/month forever), DynamoDB (25GB forever)
- Google Cloud Free → e2-micro VM (forever), $300 credit
- Cloudflare Free → Workers, Pages, R2 (10GB), Tunnel, KV
- LocalStack → Full AWS simulation offline
- Laptop (WSL2 + Docker) → Primary compute for all local work
- Minikube / kind → Kubernetes clusters locally
- All tools → 100% open source
The goal: prove that serious cloud engineering skills can be built without spending money on infrastructure. The learning, not the budget, is the differentiator.
| Week | Phase | Projects Completed |
|---|---|---|
| Week 1 | Phase 0 | p01 |
This table updates every week.
I document every phase publicly — on GitHub (here) and on LinkedIn.
If you're on a similar journey, hiring cloud engineers remotely, or just want to follow along:
- LinkedIn: linkedin.com/in/azwa-luwu-4849033a3
- Open to: Remote & On location Cloud Engineer · DevOps Engineer · Platform Engineer · SRE roles globally
All project repositories in this journey are open source under the MIT License. Use anything you find useful.
Built in public. Documented honestly. $0 infrastructure.