---
title: "David Cletus (@4thman) | Hashnode"
description: "Cloud & DevOps enthusiast passionate about scalable systems, automation, and building sleek web & mobile applications."
url: "https://hashnode.com/@4thman"
---

@4thman

# David Cletus

@4thman · Lagos, Nigeria · Joined May 2026

Cloud & DevOps enthusiast passionate about scalable systems, automation, and building sleek web & mobile applications.

### [Hands-On AWS: Spin Up IAM, S3 and a Jenkins Server on EC2 (and Fix What Breaks)](https://davidcloudjourney.hashnode.dev/hands-on-aws-spin-up-iam-s3-and-a-jenkins-server-on-ec2-and-fix-what-breaks?utm_source=hashnode&utm_medium=feed)

A step-by-step AWS lab with lots screenshots: create and delete an IAM user, host a site on S3, launch an EC2 server and run Jenkins on it, including the two errors I hit and how I fixed them.

26 min read · [davidcloudjourney.hashnode.dev](https://davidcloudjourney.hashnode.dev/hands-on-aws-spin-up-iam-s3-and-a-jenkins-server-on-ec2-and-fix-what-breaks?utm_source=hashnode&utm_medium=feed)

[Oct 14](https://hashnode.com/posts/hands-on-aws-spin-up-iam-s3-and-a-jenkins-server-on-ec2-and-fix-what-breaks/6ad00950178e80a42b2fc2e5)

### [From “It Works on My Machine” to Azure: Deploying a Dockerized Notes App in 3 Ways, Breaking Things, Fixing Them, and Learning Along the Way](https://davidcloudjourney.hashnode.dev/dockerized-notes-app-azure-deployment-3-ways?utm_source=hashnode&utm_medium=feed)

Docker Compose, Azure App Service with managed PostgreSQL, and a plain Ubuntu VM: one app, three deployments, and every error along the way.

22 min read · [davidcloudjourney.hashnode.dev](https://davidcloudjourney.hashnode.dev/dockerized-notes-app-azure-deployment-3-ways?utm_source=hashnode&utm_medium=feed)

[Oct 1](https://hashnode.com/posts/dockerized-notes-app-azure-deployment-3-ways/6abeed7ecbac3ed455205c57)

### [Dockerizing a Node App & Shipping It to Azure: Build, Break, Fix & Ship (3 Errors, Zero Regrets) 🐳](https://davidcloudjourney.hashnode.dev/dockerizing-a-node-app-shipping-it-to-azure-build-break-fix-ship-3-errors-zero-regrets?utm_source=hashnode&utm_medium=feed)

I wanted a hands-on project to actually cement what I'd been learning in Docker and Azure, build something small, break it, fix it, and ship it for real. So I built Container Vibes: a tiny Express app that hands you a random "vibe" (a color theme + a little quote) every time you click a button. It's deliberately simple. The point was never the app it was everything around it: containerizing it properly, pushing it to a registry, and getting it running live on Azure Container Instances (ACI). This post walks through the entire build, step by step, in the exact order I actually did it including the three errors I ran into along the way and exactly how I diagnosed and fixed each one.

14 min read · [davidcloudjourney.hashnode.dev](https://davidcloudjourney.hashnode.dev/dockerizing-a-node-app-shipping-it-to-azure-build-break-fix-ship-3-errors-zero-regrets?utm_source=hashnode&utm_medium=feed)

[2](https://hashnode.com/posts/dockerizing-a-node-app-shipping-it-to-azure-build-break-fix-ship-3-errors-zero-regrets/6ab715ee33ffa1cbad702101) [Sep 26](https://hashnode.com/posts/dockerizing-a-node-app-shipping-it-to-azure-build-break-fix-ship-3-errors-zero-regrets/6ab715ee33ffa1cbad702101)

### [I Built a One-Click Azure CI/CD Pipeline with Terraform & GitHub Actions From git push to a Live Website](https://davidcloudjourney.hashnode.dev/i-built-a-one-click-azure-ci-cd-pipeline-with-terraform-github-actions-from-git-push-to-a-live-website?utm_source=hashnode&utm_medium=feed)

A few weeks ago I built an Azure VM with Terraform from my laptop. It worked, but I still had to SSH in, install nginx and copy my website over by hand. This time I wanted all of that to happen on its own. I run git push from Git Bash, and a live website shows up on a brand new VM. The website is a copy of a public GitHub project called Omnifood, and the workflow clones it onto the server for me. No portal clicking, no SSH from me. It took me a few hours and a lot of red error messages. In this post I'll show you what worked, what broke, and how I destroyed everything at the end so Azure doesn't charge me for a VM I forgot about. (The name "Hagital" comes from my school, Hagital Tech Institute. Use your own names when you follow along.)

20 min read · [davidcloudjourney.hashnode.dev](https://davidcloudjourney.hashnode.dev/i-built-a-one-click-azure-ci-cd-pipeline-with-terraform-github-actions-from-git-push-to-a-live-website?utm_source=hashnode&utm_medium=feed)

[Sep 20](https://hashnode.com/posts/i-built-a-one-click-azure-ci-cd-pipeline-with-terraform-github-actions-from-git-push-to-a-live-website/6aaf399f4ce2d128e9173d61)

### [Three Days, Four Errors, One Working Azure VM: Deploying with Terraform and Remote State](https://davidcloudjourney.hashnode.dev/three-days-four-errors-one-working-azure-vm-deploying-with-terraform-and-remote-state?utm_source=hashnode&utm_medium=feed)

This was my first real hands-on Terraform assignment: deploy a working Azure VM, wire up a remote backend for the state file, and document the whole process. On paper it looked like a weekend task. It took me close to three days, mostly because I kept running into errors I'd never seen before and had to actually understand each one instead of working around it. This post walks through what I built, the order I built it in, the four errors that stopped me at different points, how I got past each one, and the proof that it all worked in the end. Repo: github.com/4thman/cloud-cohort

13 min read · [davidcloudjourney.hashnode.dev](https://davidcloudjourney.hashnode.dev/three-days-four-errors-one-working-azure-vm-deploying-with-terraform-and-remote-state?utm_source=hashnode&utm_medium=feed)

[Sep 9](https://hashnode.com/posts/three-days-four-errors-one-working-azure-vm-deploying-with-terraform-and-remote-state/6aa1579979279c27de8e1a0f)
