Self-deploying app on AWS
Every push to main is tested, containerized and rolled out to ECS Fargate by GitHub Actions. Authenticated with GitHub OIDC — no stored AWS keys — and rolled back by image tag.
CI/CD pipelines, Infrastructure as Code and AWS. BCIT CIT diploma, AWS certified, based in Vancouver — looking for a DevOps or Cloud Engineer role.
AWS Solutions Architect – Associate·BCIT · Computer Information Technology
Every push to main is tested, containerized and rolled out to ECS Fargate by GitHub Actions. Authenticated with GitHub OIDC — no stored AWS keys — and rolled back by image tag.
A segmented VPC with a load balancer, a private application server reached only through Session Manager, and a private database. Monitored with CloudWatch alarms that were tested by inducing the failures — and five real incidents, root-caused and written up.
A document versioning tool for a real QA process at my workplace — a React/TypeScript frontend built against a versioned-upload, role-based API, orchestrated with Docker Compose alongside Postgres. Backend in active development.
BCIT-era infrastructure projects — a Packer + Terraform three-tier deploy, Ansible roles on Vagrant, and a five-service Kafka system behind Nginx.
Before this, I spent several years in hands-on, high-accountability work — production and sanitation at a bakery, logistics as an Amazon delivery associate, and a stint in security — jobs that taught me to show up, follow procedure exactly, and stay calm when something breaks. In 2022 I completed a Diploma in Computer Information Technology at BCIT, infrastructure track: Linux and Windows Server administration, enterprise networking, cloud computing and system provisioning. Through BCIT's industry project program I built an internal portal for WorkSafeBC in C# and ASP.NET with a team of five.
This year I earned the AWS Solutions Architect – Associate and built the projects above — a CI/CD pipeline to ECS Fargate, a segmented three-tier VPC, a Dockerized internal tool — to put it into practice. I like automating the manual step, writing infrastructure as code instead of clicking through a console, and fixing the root cause rather than the symptom.