Preface I’ve been developing Cloud Inventory on-and-off for about half a year at this point as a sort of pandemic-project. The concept has been something I’ve wanted to tackle for years now, having interacted with a few different Cloud CMDBs, and always having wanted more out of them. After the initial prototype was complete, I deployed it on a contract with the Environmental Protection Agency (EPA) to help track their cloud footprint over time as they were migrating systems to AWS and Azure.

In my spare time I’ve been working on some tools written in Go which sniff network packets from enthusiast home routers and export flow metadata to a collection system running in AWS, allowing for real-time querying of network traffic. The source code for the systems talked about in this post can be found at https://github.com/sheacloud/go-flowprobe and https://github.com/sheacloud/flowsys TL;DR On-and-off over the past 1-2 years I’ve been building a collection of tools which allows for tracking network flows across my home router.

I recently decided to set up a personal website to showcase some of the projects I’ve been working on, and get a better hands-on understanding of static content hosting. In this post I’ll walk through how I got the site set up, what technologies are being used, and some of the issues I ran into. All of the code for both the website, and the terraform used to deploy the website, can be found here