This post is the first in a series that is going to talk about best practices for managing your AWS infrastructure and applications. This is an entry level guide and is not meant to make someone an expert, but rather to give people that are just getting started a foundation of best practices.
The public cloud in general, and AWS in particular are changing the way that systems administrators think about the infrastructure that they manage and the applications that run on that infrastructure. Things are becoming far less permanent and more ephemeral and temporary. We now deal in instances that last until the next deployment instead of servers that are bought every 3-5 years. We now purpose build resources for an application instead of making a new application fit on existing hardware resources. This requires a new approach and new best practices.
What are we talking about when we are talking