PoC||GTFO

If you are unfamiliar with the International Journal of Proof-of-Concept or Get The F*ck Out (my edit) then I encourage you, dear reader, to become familiar with it. It is a great read by hackers for hackers.

Long story short

One thing geeks like myself have taken to doing, is preserving the history of the internet by replicating information to sites and servers with better control. That is why I have created this repo, which automatically updates daily (thanks Github Workflows!)

Happy to announce that my Github Action utahcon/action-hugo has been updated to now support Hugo Modules. This change basically means there is now an on-board implementation of Golang, and git. Nothing too scary. Didn’t increase build times by too much, nor does it impact the way you use the action, except that it now support Modules. Enjoy!

Link: utahcon/action-hugo:v0.80.0

2021 Had Different Ideas

Welcome to 2021, I decided to post about my plans to blog a bit more in 2021, but the internet gods had conspired against me and made my Github Action action-scp fail. So I started into fixing it. If you see this blog post, it is indeed fixed.

What happened?

No clue, but something on the Github side of things changed in a way that I was starting to fail host key verification, even though it specifically uses StrictHostKeyChecking=no. What to do? Play around.

A New Year

It has been a rough one, not for me personally, I actually can’t complain about 2020 too much. Aside from being locked in closer quarters than normal with my kids, the year was overly meh. I will go count my blessings and keep at it.

New Goals

Aside from the normal weight loss, education, etc. goals, I am also committing, once again to 52 posts on this blog this year. I am not going to make any commitment to the content of these posts, but I will generally try to keep them tied (at least in general) to tech and my thoughts on tech. Hopefully I will get the chance to sprinkle in some cloudy stuff, and some Golang stuff as I go. For now, I will just say, at least 1 post per week (yeah, I realize I already missed a week, I’ll make it up).

I am proud to announce that I have completed my first Microsoft Azure Certification.

To see more of my certifications checkout the certifications page.

Well it is working if you are seeing this. More on that later.

AWS provides a handy Git based repository to their customers called CodeCommit. Accessing the repository is easy enough, upload your SSH Key to the AWS Console, and then add CodeCommit to your SSH configuration:

# ~/.ssh/config
Host git-codecommit.*.amazonaws.com
User USER1EXAMPLEARN1
IdentityFile ~/.ssh/USER1EXAMPLEARN1_rsa

This is wonderful until you need to access more than one AWS Account’s CodeCommit repo. How do you identify between two different AWS Account repos that use the same URL? You update your SSH configuration like this:

This is a temporary post to let me know that my Github Actions are functional. Yay me!

Maybe you are lazy like I am, but when I want to read the Boto3 documentation I just open my browser, and in the omnibar I type boto3 and slap Enter; however, this results in my browser auto-filling the URL bar with https://boto3.amazonaws.com and since the AWS guys are too lazy to add a redirect there, I have created a simple User Script that does exactly that, it just redirects the browser to the correct link https://boto3.amazonaws.com/v1/documentation/api/latest/index.html

Building off my last post GNU Parallel and AWS CLI, today I used parallel with more AWS to get a count of all AMIs being used in my infrastructure using any in-house AMI (non-Amazon, non-Marketplace).

The Problem

I need to know how many of my instances are running Chef clients. Conveniently we only run Chef client on instances that use images we have created in-house. So I can limit my search. While I could have done this with a well thought out one-liner I thought it would be more usable as a bash script.