Skip to content

Abdimajid Hussein

DevOps Engineer

London, UK

Infrastructure you can explain. Delivery you can repeat.

I build cloud platforms with Terraform, automated pipelines and GitOps, and trace failures back to their root cause.

  • 2 completed platforms
  • ECS + EKS
  • GitOps
  • Observability

01About

I am a DevOps Engineer focused on building clear, repeatable infrastructure on cloud platforms.

I build platforms with Terraform, containers and Kubernetes, covering private networking, automated delivery, GitOps and observability from infrastructure through to running workloads.

When something breaks, I trace it through the network, the application and the delivery path until I find the root cause.

02Projects

Selected engineering work.

Two completed platforms, from Terraform to running workloads.

01Completed

Snipe-IT on AWS ECS Fargate

A production-style deployment of the open-source Snipe-IT asset manager on AWS. ECS Fargate runs in private subnets behind an HTTPS load balancer with RDS for persistence and GitHub Actions handling delivery.

  • AWS
  • Terraform
  • ECS Fargate
  • Docker
  • RDS
  • GitHub Actions
  • OIDC
  • 8 reusable Terraform modules
  • 4 GitHub Actions workflows
  • OIDC authentication with AWS instead of stored long-lived AWS credentials

Request path

  1. User
  2. Route 53
  3. HTTPS Application Load Balancer
  4. Snipe-IT task on ECS Fargate

Private infrastructure

  • Fargate tasks in private subnets
  • Amazon RDS
  • NAT gateway for outbound

Deployment flow · separate from requests

  1. GitHub Actions
  2. OIDC to AWS
  3. Amazon ECR
  4. ECS service deploy
02Completed

Amazon EKS Application Platform

A Kubernetes platform on Amazon EKS running the 2048 web app on private worker nodes. Terraform provisions the infrastructure, GitHub Actions builds and scans images, Argo CD deploys Helm charts from Git, and Prometheus and Grafana provide visibility.

  • AWS
  • EKS
  • Terraform
  • Kubernetes
  • Helm
  • NGINX Ingress
  • Argo CD
  • Prometheus
  • Grafana
  • GitOps delivery: CI builds, Argo CD deploys
  • Automated DNS and TLS with ExternalDNS and cert-manager
  • Trivy gate blocks HIGH and CRITICAL image vulnerabilities

Request path

  1. User
  2. Route 53
  3. AWS load balancer
  4. NGINX Ingress
  5. ClusterIP Service
  6. 2048 app pods

Private subnets

  • EKS worker nodes
  • NAT gateway for outbound

Operations, not in request path

  • Argo CD (GitOps)
  • Prometheus
  • Grafana

Deployment flow · separate from requests

  1. GitHub Actions
  2. Trivy scan
  3. Amazon ECR
  4. Helm values in Git
  5. Argo CD sync

03Tools

Tools I use, and what for.

01 Cloud & Infrastructure

  • AWS
  • Terraform

02 Containers

  • Docker
  • ECS Fargate
  • Kubernetes
  • Amazon EKS
  • Helm

03 Delivery

  • GitHub Actions
  • Argo CD
  • GitOps

04 Observability

  • Prometheus
  • Grafana
  • CloudWatch

05 Networking & Security

  • VPC
  • ALB
  • Route 53
  • IAM
  • Security Groups
  • OIDC
  • HTTPS / TLS

06 Systems

  • Linux
  • Bash
  • Python
  • Git

04Building

Currently building.

In progressSystem designSREDevSecOpsFinOps

Production Reliability Platform

I'm taking a service beyond 'it deploys' and focusing on how it is operated: reliability targets, observability, security, cost and recovery.

Planned scope · not yet built

05Contact

Building a platform team? Let's talk.

Open to DevOps, Platform and Cloud Engineering roles. Email is the quickest way to reach me: abdimajid819@gmail.com