Cloud Engineer & DevOps Engineer
I help engineering teams ship faster and break less.
I turn manual, error-prone deployments into automated,
version-controlled pipelines on AWS — with security checks,
monitoring, and a sharp eye on the cloud bill built in.
A great engineer should do more than run commands — they should remove friction for the whole team. Here's how I move the needle from day one.
I replace fragile, hand-run deployments with CI/CD pipelines that build, test, scan, and ship on every commit. When a team I worked with ran out of GitHub Actions minutes, I stood up a self-hosted runner so delivery never stalled.
Every environment I build is defined in Terraform — VPCs, EKS clusters, IAM, RDS — so it's reproducible, reviewable, and free of configuration drift. Spin it up, tear it down, rebuild it identically. No tribal knowledge, no surprises.
With a background in security monitoring and incident response, I shift security left — image scanning with Trivy, policy enforcement with Kyverno, and least-privilege IAM by default. Safe and fast aren't a trade-off.
Idle resources are wasted money. I right-size instances, decommission demo environments when they're done, and design for cost from the start — so the architecture stays lean without sacrificing reliability.
I instrument systems with Prometheus, Grafana, and CloudWatch so teams see problems before users do. Dashboards and alerts mean less firefighting and faster, calmer recovery when something does break.
As an assistant team lead on a 20-engineer build, I unblocked teammates, documented the deployment process, and turned recurring "it's broken again" issues into permanent fixes. I make the people around me faster, not just myself.
A self-updating dashboard that scouts remote DevOps & cloud roles daily, scores each posting against my skill stack, and filters out US-authorization-only roles. Built entirely on free infrastructure — no cloud bill, no server needed.
Deployed a full-stack banking application to AWS EKS, containerizing the React frontend with Docker, pushing versioned images to ECR, and rolling out releases with kubectl. Owned the manual deployment workflow when CI minutes ran out, resolved recurring stale-image and routing bugs, and documented the process so the whole team could ship. Demo environment was later decommissioned to eliminate idle cloud spend.
Built a complete delivery pipeline that takes code from commit to a running EKS cluster automatically. Integrated SonarQube quality gates and Trivy image scanning to block bad builds before they ship, with all underlying AWS infrastructure provisioned by Terraform and a self-hosted runner for uninterrupted delivery.
Provisioned a production-style Kubernetes cluster on AWS EKS with Terraform, deployed workloads via Helm, and wired up Prometheus and Grafana so the cluster's health was visible at a glance — catching resource issues before they became outages.
I'm Jideofor Onyekachi Peter, a Cloud and DevOps Engineer who builds and automates infrastructure on AWS — and who cares as much about the team shipping it as the systems themselves.
I've deployed containerized applications to Kubernetes on EKS, provisioned full environments with Terraform, and built CI/CD pipelines with security and quality gates wired in. A background in security monitoring and incident response means I think about what can go wrong before it does.
I work the way good operations teams do: automate the repetitive, make systems observable, keep costs honest, and document everything so knowledge doesn't live in one person's head. I'm always learning and leveling up, and I'm looking for a role where I can take ownership of infrastructure and help a team move faster with confidence.
Open to Cloud & DevOps opportunities, freelance infrastructure projects, and collaborations. Feel free to reach out!