I've been building and maintaining technical infrastructure since the late 90's, which means I have spent a lot of time wondering "How can I make X better?", "Why isn't Y working?", and "What is paging me at 3AM?". I've also spent a lot of time thinking about how I can help others learn systems administration topics in a less painful way.
I'm currently writing an ebook called AWS Architecture about designing and implementing reliable, secure systems on Amazon Web Services. Even with a background in systems administration, there has been a lot to learn about building systems on top of AWS since I started using it in 2007. Although AWS makes things like scaling quickly easier, building resilient systems still takes work and there are a lot of "gotchas" you can stumble on along the way.
Many systems administrators, developers, and technical managers struggle when getting started with Amazon Web Services — I know I sure did. Getting up to speed on terminology, architecture design patterns, and everything else involved with AWS by reading through the mountains of Amazon documentation in a short time period is tough.
If you are already using AWS, you know it can be hard to stay on top of the best practices. Amazon puts out a lot of great content and training resources, but having it all boiled down to the essentials makes a big difference.
My new site, AWS Architecture, is devoted to the upcoming ebook and sharing knowledge about Amazon Web Services. Head over there and sign up for my free 30 day course about AWS best practices and you'll also be the first to know when the book is released.