second post in the training tracker series: before adding a single new feature, the working single-user app gets a proper security review. What an audit of a small web app actually looks at, and why shipping something is the start of the job, not the end of it.
first post in the training tracker series: provisioning the AWS infrastructure, designing the data model, and seeding 105 days of plan data into DynamoDB.
A personal habit tracker built around a 15-week run/walk training plan — and a vehicle to learn DynamoDB, Lambda, Cognito, and the Claude API by building something I open every day.
A billing audit of the tacedata.ca AWS account that found $59/month in infrastructure charges on a site that was supposed to cost nearly nothing — and reduced it to $3.63/month.
Setting up server-side traffic analytics for tacedata.ca — and hitting a hard wall in the CloudFront Free pricing plan that blocks all logging features.
Attempting server-side traffic analytics for tacedata.ca using CloudFront access logs and AWS Athena — and what the CloudFront Free pricing plan actually allows.
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.
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.