Cloud & DevOps Engineer specializing in Infrastructure as Code, AWS, Kubernetes, Docker, Terraform, and CI/CD — I design, automate, and ship the systems most people only draw on a whiteboard.
Every diagram below traces the actual data path of a deployed system — provisioned with Terraform, shipped through GitHub Actions.
A live e-commerce app on a real custom domain — ArgoCD watches the repo and syncs the cluster automatically, CloudFront and ACM front it, and CloudWatch/Prometheus/Grafana keep watch across five Terraform-managed environments.
A FastAPI + PostgreSQL service on ECS Fargate, provisioned entirely by Terraform with no manual console changes. GitHub Actions authenticates via OIDC federation — no stored AWS keys — gated by tests and a manual production-approval step.
A Node.js restaurant application deployed like a real production system — Docker → EKS, with Terraform-provisioned VPC, ECR, and RDS, and Prometheus/Grafana watching it the whole way.
A Java 17 / Spring WAR, built with Maven, deployed to ECS on Fargate — zero EC2 instances to patch. Application Load Balancer in front, CloudWatch logging every request.
An AWS-first, fully event-driven reference architecture. Upload hits S3, a queue with a dead-letter safety net feeds Lambda, and DynamoDB + SNS close the loop — no servers, no idle cost.
A cost-optimized EKS cluster on Kubernetes 1.31, built with the terraform-aws-modules registry module — no NAT Gateway, public nodes, and an autoscaling node group for fast, cheap iteration.
A responsive bakery site built for a real client — static front end, direct-to-WhatsApp ordering, and a Supabase client already wired in as the foundation for what's next.