About

A bit more detail

I'm a cybersecurity student and IT support specialist in the Minneapolis–St. Paul area, working toward DevSecOps and cloud security. My interest sits where delivery meets security: the pipeline that ships the code is also the best place to stop bad code from shipping.

Most of what I know came from building things end to end rather than following along. I built a Kubernetes cluster by hand with kubeadm before touching a managed service — distributing certificates, configuring CNI, hardening nodes — and it made every managed offering legible afterwards. The same pattern repeats across my projects: provision it with Terraform, deploy it with a pipeline, then write down what broke.

Lately the focus has been supply-chain security and GitOps: federating CI to AWS with OIDC instead of static keys, signing images with keyless Cosign, and letting Argo CD reconcile rather than giving the pipeline cluster credentials. Alongside that I hold Security+ and Network+, and I'm working through the AWS Solutions Architect – Associate.

I'm looking for a DevSecOps or cloud security role on a team where that kind of work is valued rather than deferred to a quarterly audit.

Resume ↓ GitHub LinkedIn

01Experience & learning

  • [EDIT ME] Present

    IT Support Specialist

    Company name

    Two sentences on what you own day to day, then one concrete outcome. Numbers beat adjectives — "cut ticket resolution time from 3 days to 8 hours" lands harder than "improved support efficiency".

  • [EDIT ME]

    Cybersecurity studies

    School / programme name

    Coursework and focus areas. Mention anything hands-on — labs, competitions, capstone projects — rather than just listing module titles.

  • 2026

    CodePath AI-110 — Foundations of AI Engineering

    Instructor-led programme, built around Anthropic's Claude

    Five project modules building on each other: debugging deliberately broken AI-generated code, designing an OOP system from a UML diagram, building a content-based recommender with a model card and bias analysis, and an agentic bug-analysis tool with a risk assessor. The capstone extended my Module 3 recommender into VibeMatch AI Concierge — an LLM planning step, output guardrails, and an evaluation harness, with the ranking left deterministic.

  • 2025 — 2026

    AWS Job-Oriented Program

    12-week structured programme

    Weekly labs across IAM and account hardening, EC2, storage (S3/EFS/EBS), networking, and cost management — each with written notes and interview preparation.

  • 2023 — present

    Independent cloud & DevOps projects

    Published on Medium and GitHub

    Terraform-provisioned EKS and AKS clusters, GitOps delivery with Argo CD, multi-tenant AWS infrastructure, and a self-hosted homelab — each written up so someone else can reproduce it.

02Certifications

  • CompTIA Security+
  • CompTIA Network+
  • AWS Solutions Architect – Associate in progress

03How I work

Infrastructure is code or it doesn't exist

If it was clicked in a console, nobody can review it, reproduce it, or roll it back. Everything goes through a plan and a pull request.

Security gates, not security reports

A scanner that only warns gets ignored by week three. Pipelines should fail closed, with a documented exception path for the cases that matter.

Build it the hard way once

kubeadm before EKS, manual certificates before cert-manager. The abstraction is only safe to trust once you know what it's abstracting.

Write the runbook while it's fresh

Documentation written a month later is fiction. I write the steps as I take them, including what broke.

$ ping abdurahim

Let's build something secure.

Open to DevSecOps and cloud security roles, collaborations, and freelance infrastructure work. Based in Minneapolis–St. Paul, MN.

Message me on LinkedIn yonghoabdurahim@gmail.com GitHub Medium dev.to