The Well-Architected Review Explained
What is the Well Architected Review?
Jeremy:
When I talk to my clients about what it means to be well architected and what that review really consist of- we’re looking at a number of things across the infrastructure, and is their infrastructure well architected according to AWS best practices standards. Its act a 42-point check list where our team is going through line by line, infrastructure piece by infrastructure piece to basically say, yes or no, and then what are the recommendations, or steps needed in order to become well architected.
As we progress on the journey together, it actually reveals things that sometimes sit outside the scope of the Well Architected Review. There might be other opportunities for saving beyond what a well architected framework would look like such as an opportunity for automation or a new big data tool. We are looking at everything and as we push them forward in this journey we learn more and we build the trust within our client base and we are able to craft their cloud journey from there.
Alex:
What I usually see, is that you want to get a well architected, there are some people who don’t necessarily want to preform it, because it does shed light on a lot of security networking best practices and architecture. If you don’t have full engagement between your CISO (chief information security officer), and IT department, and you are working around them, they’re going to ask the same questions the well architected review is asking.
The Well Architected Review is helping them legitimize the workload, especially if it’s something like using phantom IT on a project you are doing on an off-shoot, because it is going to grow, and chances are, it’s going to be successful. At the end of the day, that is what the cloud is for, it’s for being able to move fast, be agile and do it in a safe manner, probably even safer than their own data centers