[{"content":"The scenario A sandbox environment for testing Azure Virtual WAN routing — two spokes, each connected to its own virtual hub, each hub with its own route table. Enough moving parts (management groups, VNETs, a Virtual WAN, two hubs, hub connections, and test VMs) that hand-clicking it in the portal isn\u0026amp;rsquo;t something I wanted to repeat, so it\u0026amp;rsquo;s all Terraform.\nOne deliberate wrinkle worth calling out: VNET-HUB — the plain virtual network sitting alongside the Virtual WAN resource — is …","date":"2026-08-27","permalink":"/posts/vwan-sandbox-terraform/","summary":"Modeling a two-hub Virtual WAN sandbox in Terraform: management group placement, per-spoke virtual hubs with their own route tables, and the RDP-reachable test VMs used to validate connectivity.","tags":["azure","terraform","networking","vwan","iac"],"title":"Building a Hub-and-Spoke Sandbox on Azure Virtual WAN with Terraform"},{"content":"Why this setup This site is a static Hugo build. The obvious way to host that is aws s3 website-endpoint with a public bucket. I didn\u0026amp;rsquo;t do that, for a few reasons:\nNo native HTTPS on the S3 website endpoint No custom domain without extra DNS gymnastics A public bucket is a wider blast radius than it needs to be No caching/edge distribution, so every visitor round-trips to us-east-1 (or wherever the bucket lives) Instead, the stack is:\nRoute 53 (DNS) → CloudFront (CDN + TLS) → S3 (private …","date":"2026-08-27","permalink":"/posts/deploying-this-site-on-s3-cloudfront/","summary":"The architecture and pipeline behind this site: a private S3 bucket, CloudFront with Origin Access Control, and a GitHub Actions deploy using short-lived OIDC credentials instead of static access …","tags":["aws","s3","cloudfront","terraform","ci-cd"],"title":"How I Deploy This Site: S3 + CloudFront + GitHub Actions OIDC"},{"content":"Quick test, not a rigorous benchmark — just logging numbers before I forget them. Tagged lab-note — shorter and rougher than the full write-ups, filterable via the tag search on the posts page.\nSetup Uploading a 500MB file from a home connection in Jakarta Target bucket in ap-southeast-1 (Singapore) Compared: direct aws s3 cp vs the same command against the *.s3-accelerate.amazonaws.com endpoint 5 runs each, averaged, network otherwise idle Results Method Avg time Avg throughput Direct upload …","date":"2026-08-20","permalink":"/posts/benchmarking-s3-transfer-acceleration/","summary":"Rough numbers comparing S3 Transfer Acceleration against a direct regional upload from Jakarta to an ap-southeast-1 bucket.","tags":["aws","s3","networking","benchmarking","lab-note"],"title":"Quick Bench: S3 Transfer Acceleration vs Direct Upload"}]