Portrait of David Prosper Isinguzo

Cloud DevOps Engineer · Lagos, Nigeria · Remote-first

David Prosper
Isinguzo

If it can't be reviewed in a pull request, it isn't solved yet.

I design and operate cloud infrastructure on AWS and Azure — modular Terraform, Ansible, and Kubernetes on EKS — and build the CI/CD pipelines that ship it with security gates on every push. I work where infrastructure automation meets platform reliability: finding the manual step, deleting it, and writing down what broke so it doesn't break twice.

Contact me Download CV Read the blog Projects
KCNA — CNCF, valid to 2028 The Linux Foundation — LFS250 · LFS158 · LFC102 
$ terraform output
role     = "cloud-devops-engineer"
status   = "operational"
location = "lagos-ng · remote-first"
$

about

Infrastructure as code.
Reliability as habit.

Who I am

I'm a DevOps engineer with production experience designing and operating cloud infrastructure across AWS and Azure. My work sits at the intersection of infrastructure automation, CI/CD engineering, and platform reliability — building systems that are repeatable, auditable, and safe to deploy on a Friday.

What I do

  • Design and operate cloud infrastructure on AWS and Azure — modular Terraform, Ansible, and Kubernetes on EKS.
  • Build the CI/CD pipelines that ship it, with security gates on every push.
  • Structure Terraform modules and write Ansible roles so an environment can be rebuilt from scratch, not repaired by hand.
  • Run containerised workloads with Prometheus and Grafana in front of them, so failures are visible before users report them.
  • Diagnose production incidents and write the fix up as a runbook the team can reuse.

What I care about

  • If a change can't be expressed as code, reviewed in a pull request, and deployed repeatably, it isn't solved yet.
  • Green pipelines don't always tell the full story — a successful run and a working system are two different claims.
  • Find the manual step and delete it, then write down what broke so it doesn't break twice.
based in
Lagos, Nigeria
working
Remote or hybrid
focus
DevOps · Cloud · Platform
education
B.Sc Computer Science, University of the People (2026–2029)
core stack
AWS · Terraform · Kubernetes · GitHub Actions · Linux

experience

Where I've shipped.

Jan 2026 – Jun 2026

DevOps Engineer

The CloudAdvisory Oy · Helsinki, Finland (Remote)

  • Provisioned multi-environment AWS infrastructure (VPC, EKS, RDS, ECR, IAM/IRSA, Route53, ACM) with modular Terraform and Ansible on an S3 remote backend with DynamoDB locking, cutting new environment provisioning from several days to under 30 minutes.
  • Isolated shared state in a bootstrap module so a terraform destroy on dev or prod could not wipe the backend.
  • Designed and maintained GitHub Actions CI/CD pipelines — Semgrep SAST, Maven tests, Docker builds, Trivy scans with a hard fail on HIGH/CRITICAL CVEs, and Helm deploys — with branch-based routing to dev and production.
  • Authored Kubernetes manifests and Helm charts for 9 Spring Boot microservices (Deployments, Services, NetworkPolicies, PDBs, per-environment HPAs) across isolated dev and prod environments on Amazon EKS.
  • Deployed Prometheus and Grafana via kube-prometheus-stack, giving the team real-time visibility across 30+ Kubernetes workloads and exposing dashboards through ALB Ingress with ACM wildcard TLS and external-dns against a Route53 hosted zone.
  • Migrated 20+ application secrets to AWS Secrets Manager via External Secrets Operator and IRSA, eliminating plaintext credential exposure, and remediated HIGH/CRITICAL CVEs across Tomcat, Netty, Spring Cloud Config, Spring AI, and MCP Core.
  • Diagnosed CrashLoopBackOff and init-container failures by tracing pod events and tuning liveness/readiness probes, timeouts, and startup ordering — resolving production incidents without escalation.
  • Wrote Python and Bash automation for provisioning, secret rotation, and pipeline tooling, and enforced a feature→dev→main Git flow with PR-gated Trivy/Checkov scanning and Terraform plan output auto-posted to every PR.

skills

The working stack.

cloud

  • AWS
  • EC2
  • VPC
  • EKS
  • RDS
  • ECR
  • S3
  • IAM / IRSA
  • Route53
  • ACM
  • CloudWatch
  • Azure

infrastructure as code

  • Terraform
  • Remote state / S3 backend
  • DynamoDB locking
  • Ansible

containers & orchestration

  • Docker
  • Docker Compose
  • Kubernetes
  • Helm
  • External Secrets Operator

ci/cd

  • GitHub Actions
  • OIDC
  • Semgrep
  • Trivy
  • Checkov
  • Azure DevOps Pipelines

observability

  • Prometheus
  • Grafana
  • kube-prometheus-stack
  • CloudWatch

platform & languages

  • Ubuntu Linux
  • Bash
  • Python
  • JavaScript / TypeScript
  • YAML
  • Nginx
  • external-dns
  • PostgreSQL
  • MySQL
  • MongoDB
  • Git

projects

Built and shipped.

AWS · Terraform

Three-Tier AWS Infrastructure

A modular three-tier AWS application — VPC subnetting, IAM, ALB, DNS and SSL — running EC2 with RDS MySQL, with public and internal ALB segmentation enforced through security groups. Resolved a Terraform security-group dependency cycle by refactoring to aws_security_group_rule and using terraform import, with zero manual state edits.

  • Terraform
  • VPC
  • EC2
  • RDS MySQL
  • ALB
  • IAM
  • ACM
View on GitHub →

certifications

Verified, and current.

blog

Runbooks, not think pieces.

First posts are in progress — production incidents written up as runbooks. Check back shortly.

Go to the blog

contact

Let's talk infrastructure.

Open to mid-level DevOps, Cloud, and Platform Engineering roles, remote or hybrid. If you have a pipeline that keeps breaking or a stack that isn't in code yet, that's the conversation I want.