backend/tests/test_drift_engine.py
Terraform state parser and drift-engine regression tests
Inspect original source ↗Infrastructure reconciliation
DriftGuard
Terraform drift detection and review-based remediation for AWS infrastructure.
PLATFORM / DEVOPS ENGINEER · LAGOS, NIGERIA
Platform, cloud and DevOps engineer · Backend engineering
I build cloud infrastructure, deployment pipelines and backend tools. My projects include Terraform drift detection, Kubernetes policy controls and the software that supports them.
Based in Lagos, Nigeria · Open to international remote engineering roles and scoped contracts

SELECTED WORK
backend/tests/test_drift_engine.py
Terraform state parser and drift-engine regression tests
Inspect original source ↗Infrastructure reconciliation
Terraform drift detection and review-based remediation for AWS infrastructure.
controller/internal/remediation/tier_test.go
Manual-gate policy tests that reject automatic merge
Inspect original source ↗Kubernetes / Policy enforcement
Policy-tiered Kubernetes remediation with a deliberately bounded GitOps approval path.
.github/workflows/sentinel-scan.yml
Trivy and Kubescape scan jobs with uploaded artifacts
Inspect original source ↗Kubernetes security scanning
A Kubernetes security-scanning lab combining container vulnerability and posture scan evidence with scheduled CI automation.
ENGINEERING EVIDENCE / DRIFTGUARD
DriftGuard's AWS collector could not safely treat an incomplete inventory as an empty account. A missed resource and an unknown result have different meanings.
01 / EXECUTED AWS PROVIDER DRIFT
A successful GitHub Actions run created a disposable AWS Systems Manager parameter with Terraform, changed it outside Terraform, detected the change using a refresh-only plan, and verified a redacted evidence record before cleanup.
Examine actual AWS execution logs ↗02 / MERGED FAILURE-HANDLING REGRESSION
PR #3 adds failure handling for interrupted AWS inventory collection and preserves indexed Terraform resource identities. The change includes regression tests and was merged into DriftGuard's main branch.
Inspect source changes and regression tests ↗The AWS run verifies one drift-detection workflow. PR #3 tests how DriftGuard handles incomplete AWS inventory. The scope and results are linked above.
Full DriftGuard case study ↗AREAS OF EXPERTISE / THE WORK I DO
I work across cloud infrastructure, backend APIs, deployment pipelines and operations. These examples show how I use those skills.
Internal engineering workflows, service boundaries, GitOps delivery and infrastructure-facing APIs. I focus on reducing repeated manual operations without introducing an opaque control plane.
Warden: policy-bound automation ↗CI/CD, containers, GitHub Actions, Argo CD, deployment health checks and rollback/recovery considerations. A successful build is not the same thing as a verified release.
Inspect this site's delivery workflow ↗AWS networking, IAM and resource configuration, Terraform, short-lived credentials and drift investigation. I prefer reproducible changes that can be reviewed before they reach a live environment.
DriftGuard: live state versus desired state ↗Python, FastAPI, PostgreSQL, APIs, tests and services that expose infrastructure state safely. The software must handle failed dependencies, retries, identities and incomplete results explicitly.
Review the backend implementation ↗Kubernetes deployment configuration, GitOps reconciliation, RBAC, container scanning, runtime signals and policy controls. Finding an issue and authorizing its remediation are different security boundaries.
SENTINEL: security posture investigation ↗Metrics, logs, traces, failure investigation and post-deployment verification. I treat monitoring as evidence for decisions, not proof that a system is fault-tolerant.
Read my observability research ↗Execution identity, recovery contracts and controls around automated infrastructure changes. These are active research and implementation areas, not claims of deployed autonomous production systems.
CER: execution safety research ↗PROFESSIONAL BACKGROUND / SELECTED WORK
I also take on cloud and DevOps contracts through Edwin Cloud DevOps Services. Some client work is confidential.
Independent cloud and DevOps engineering · Contract delivery, infrastructure changes, pipelines and technical handoff.
Remote DevOps contract · CI/CD operations, deployment verification and cloud application environments under team oversight.
Remote DevOps internship · Infrastructure-as-code tasks, CI support and deployment troubleshooting.
Cloud and DevOps internship · Linux, AWS application deployment and Git-based infrastructure workflows.
CLIENT CONFIDENTIALITY
Client environments and contract details stay private. My public repositories show the engineering work I can share.
See a public delivery example ↗FEATURED PUBLICATIONS
CLOUD / PLATFORM / DEVOPS / BACKEND
My projects show source code, tests and current limitations. Contact me with a role description or a scoped infrastructure problem.
WRITING
Implementation details, failures and decisions from projects in the repository.
Read articles ↗SERVICES
For teams that need help with cloud infrastructure, deployment pipelines or operating existing systems.
Services and contact ↗