AWS Documentation is Awful

This past week I had a coworker ask me to help with some Amazon Web Services (AWS) administration. I needed to go in and check the last time a handful of users had logged into the system. I had been shown how to do this in the past but didn't do a good job of taking notes. I didn't worry about it as I figured I could just use an Internet search engine to help me get the information I needed. That didn't work at all.

AWS is such a large system that there are half a dozen ways to get the information I needed. Furthermore the documentation kept saying to use a tool and write code to query log files. From my training at the beginning of the year, I knew there is an easy way to point-and-click my way to success. The thought of writing code felt like building a car before going to the grocery store to buy some eggs.

Fortunately I remembered some of what I had been taught and got roughly to the right place. Using information sent to me by my coworker I was able to stumble around for bit and get the information I needed. She sent me a screenshot and it provided the missing clues I needed.

I have a notebook that I keep for work. I write down notes from meetings and helpful hints. Naturally I wrote down all the steps to repeat how to get the information I needed. Logic follows that if I have had to get the information once, there is a good chance I will need it again. Next time I don't want to waste half an afternoon trying to figure it out.