<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Cloudfront on TACE Data</title><link>https://tacedata.ca/tags/cloudfront/</link><description>Recent content in Cloudfront on TACE Data</description><generator>Hugo</generator><language>en-CA</language><copyright>2026 TACE Data Management Inc.</copyright><lastBuildDate>Fri, 08 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://tacedata.ca/tags/cloudfront/index.xml" rel="self" type="application/rss+xml"/><item><title>aws cost management — right-sizing a personal estate</title><link>https://tacedata.ca/projects/aws-cost/</link><pubDate>Fri, 08 May 2026 00:00:00 +0000</pubDate><guid>https://tacedata.ca/projects/aws-cost/</guid><description>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.</description></item><item><title>analytics: stage 1: what the cloudfront free plan doesn't tell you</title><link>https://tacedata.ca/posts/analytics-stage-1-post/</link><pubDate>Thu, 07 May 2026 00:00:00 +0000</pubDate><guid>https://tacedata.ca/posts/analytics-stage-1-post/</guid><description>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.</description></item><item><title>traffic analytics — cloudfront logs and athena</title><link>https://tacedata.ca/projects/analytics/</link><pubDate>Thu, 07 May 2026 00:00:00 +0000</pubDate><guid>https://tacedata.ca/projects/analytics/</guid><description>Attempting server-side traffic analytics for tacedata.ca using CloudFront access logs and AWS Athena — and what the CloudFront Free pricing plan actually allows.</description></item><item><title>security remediation — what we got wrong</title><link>https://tacedata.ca/projects/security-remediation-proj/</link><pubDate>Sat, 04 Apr 2026 00:00:00 +0000</pubDate><guid>https://tacedata.ca/projects/security-remediation-proj/</guid><description>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.</description></item><item><title>site: stage 5: cutting over a website</title><link>https://tacedata.ca/posts/web-stage-5-post/</link><pubDate>Fri, 03 Apr 2026 12:00:00 +0000</pubDate><guid>https://tacedata.ca/posts/web-stage-5-post/</guid><description>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.</description></item><item><title>site: stage 4: building the site itself</title><link>https://tacedata.ca/posts/web-stage-4-post/</link><pubDate>Fri, 03 Apr 2026 06:00:00 +0000</pubDate><guid>https://tacedata.ca/posts/web-stage-4-post/</guid><description>Getting the site into a state worth sharing — PaperMod setup, profile home page, content structure, and a few problems solved along the way.</description></item><item><title>tacedata.ca — this site</title><link>https://tacedata.ca/projects/tacedata-site-proj/</link><pubDate>Fri, 03 Apr 2026 00:00:00 +0000</pubDate><guid>https://tacedata.ca/projects/tacedata-site-proj/</guid><description>A static portfolio site built with Hugo and deployed to AWS via a fully automated GitHub Actions pipeline.</description></item><item><title>site: stage 3: deploying a static site on aws</title><link>https://tacedata.ca/posts/web-stage-3-post/</link><pubDate>Thu, 02 Apr 2026 00:00:00 +0000</pubDate><guid>https://tacedata.ca/posts/web-stage-3-post/</guid><description>How we set up S3, CloudFront, and a GitHub Actions deploy pipeline for tacedata.ca — no long-lived credentials, no manual deploys.</description></item></channel></rss>