I build and investigate cloud infrastructure and platform tooling where observability, evidence quality, and safe changes matter. I work with AWS, Terraform, Python, Kubernetes, GitOps, CI/CD, infrastructure security, and software-delivery systems.

Repositories are evidence of implementation, not proof of production readiness. Each linked case study separates code and executed tests from integrations and behaviors not yet validated.

Compares Terraform state and collected AWS observations, produces structured findings, and proposes remediation through reviewable GitHub pull requests rather than applying infrastructure changes automatically.

• Merged regression fix (PR #3): fail on top-level AWS inventory enumeration errors and preserve indexed Terraform resource identities.
• Drift-engine tests and CI are publicly inspectable.
• Boundary: real cross-account AssumeRole integration and multi-tenant production operation are not established by the public checks. Some per-resource attribute-read failures still need stronger handling and tests.

Case study · Inventory failure investigation

Explores a GitOps remediation path that keeps policy enforcement and manual approval separate from the generation of proposed changes.

• Go regression tests exercise the boundary preventing automatic merge under manual-approval policy tiers.
• Go CI workflow provides a repeatable source-level validation path.
• Boundary: controller PR integration is dry-run by default; end-to-end production integration is not independently established.

Case study

Contains Trivy and Kubescape scanning artifacts, a scheduled GitHub Actions workflow, and a small report aggregation script.

• Security scanning workflow.
• Boundary: these artifacts do not establish a deployable runtime detection, observability or policy-enforcement platform.

Case study

My engineering website publishes project boundaries, implementation details, technical investigations, and delivery records. The website source includes Hugo-based static delivery, source-controlled CI checks, and GitHub Pages deployment verification.

I also provide cloud and DevOps engineering services through Edwin Cloud DevOps Services. Confidential client work is not presented as publicly verified project evidence.

• Engineering website and services
• LinkedIn
• Technical articles
• Microsoft Azure Fundamentals credential

I welcome technical review, platform/cloud engineering roles, open-source collaboration, and clearly scoped infrastructure engagements.