{"id":102,"date":"2025-07-29T15:23:15","date_gmt":"2025-07-29T19:23:15","guid":{"rendered":"https:\/\/learnwithpatrick.casa\/?p=102"},"modified":"2025-07-29T15:23:15","modified_gmt":"2025-07-29T19:23:15","slug":"automating-cycling-videos-in-aws","status":"publish","type":"post","link":"https:\/\/learnwithpatrick.casa\/?p=102","title":{"rendered":"Automating Cycling Videos in AWS"},"content":{"rendered":"\n

Sometimes you get an idea for a simple fix to make your life easier… and then that simple idea spirals out of control and becomes a massive project. I like to record my bike rides<\/a> when I travel, but I don’t travel with a lot of storage media. I do<\/em> have a NAS at home. The obvious solution would be to upload videos straight to my NAS, but I don’t want to expose my NAS to the Internet (I’m fully aware that there are secure ways to do this, but for the exercise’s sake, let’s ignore that).<\/p>\n\n\n\n

My not-as-obvious but almost-as-simple solution was to upload the videos to AWS S3, have that upload generate an SQS message, and have my NAS run a scheduled task to poll the SQS for videos to download. I did this easily, and it works great! Being honest, I spent more time getting my Synology NAS to run AWS CLI commands than I did writing the actual script to poll and download – but that adventure could be its own post. Instead, here’s the jq tidbit I used to extract the bucket name and key from the SQS message for the download commands:<\/p>\n\n\n\n