Aws

Cleaning git history removes data from your repo — but not from search engines, the Wayback Machine, or GitHub’s cache. Here is what to check.

After a security review flagged AWS identifiers committed to a public repo, we used git-filter-repo to scrub them from all 46 commits — including file content and commit messages.

A Canadian mortgage rate decision aid — eight economic indicators translated into plain-English signals.

A post-launch security review of tacedata.ca uncovered sensitive AWS identifiers committed to a public repository. This is a full account of what was exposed, how it was found, and what it took to fix it.

Setting up availability monitoring for tacedata.ca using CloudWatch Synthetics — what it is, what it costs, and how we set it up.

Introducing the new tacedata.ca — why I moved from WordPress to a static site on AWS, and what I plan to do with it.

Moving tacedata.ca from Websavers DNS to AWS Route 53 — what the cutover actually involves, and how to do it without taking the site down.

Getting the site into a state worth sharing — PaperMod setup, profile home page, content structure, and a few problems solved along the way.

A static portfolio site built with Hugo and deployed to AWS via a fully automated GitHub Actions pipeline.

How we set up S3, CloudFront, and a GitHub Actions deploy pipeline for tacedata.ca — no long-lived credentials, no manual deploys.