A Comprehensive Guide To Perform An AWS Well-Architected Review — Part 2

In the dynamic world of cloud computing, maintaining a robust and efficient architecture is paramount. The AWS Well-Architected Framework Review (WAFR) offers a structured approach to ensure that cloud architectures align with best practices, thereby supporting business objectives more effectively.

A Comprehensive Guide To Perform An AWS Well-Architected Review — Part 1

Continuing the three-part blog series on the AWS WAFR, we share insights and recommendations from extensive experience with AWS customers for a smooth and successful WAFR venture. In the first part, the focus was on preparing for the review. In this second part, the spotlight shifts to conducting the review itself, emphasizing best practices to maximize its effectiveness and efficiency.

A Recap of the Goals of an AWS WAFR

Before we dive deep into some recommendations for a successful WAFR, it’s important to recap its goal. The review aims to improve systems architectures so that these systems can better support business needs. The architecture improvement process starts by reviewing the current architecture and comparing it against best practices. You do so by answering the review questions. A set of questions for each Pillar. Based on the answers, we identify areas to improve, also called High-Risk-Issues (HRI) and Medium-Risk-Issues (MRI), that would be discussed in the coming section.

Review — The second phase of a WAFR

The second phase of the WAFR process involves conducting the actual review. This phase is critical for identifying potential issues and developing a deeper understanding of the architecture’s strengths and weaknesses. It is essential to approach the review methodically, ensuring that all relevant aspects are thoroughly examined. There are some best practices for conducting a WAFR as prescribed by AWS. Following them would make sure your review gets concluded with lots of insightful details to move on to the next phase of the process. These best practices are mentioned underneath: -

1- Set expectations

WAFR is a big-time commitment for all participants. Take the time to have this conversation with main stakeholders in advance, so they are clear on the expectations and their roles before, during and after the review. Make sure you get their support.

2- Engage in conversations, not an audit

The best results we see from WAFR sessions is when they are looked at by stakeholders as conversations, not checklists or scoring exercises. This will encourage all team members to speak openly about their systems as long as they are not blamed for missing some best practices. This will also help uncover architectural risks.

3- Treat the WAFR like a team sport

Everyone on the team should play a role. For example, a pillar sponsor should make sure that all questions in the pillar are answered correctly. The sponsor then should own the improvement plan for risks identified during the review.

4- Keep a continuous check on your infrastructure

A Well-Architected Review should not be treated like a one time effort. Things always change and should be kept in check.A practice should be adopted within the organization to conduct WAFR (or a customized version of it) on a regular basis, or following big milestones on the workload’s life cycle.

5- Earlier is better

It’s easier to influence decisions and drive changes while things are still in the design phase and not in production. Hence, timeliness in this process becomes crucial to get the best results out of the WAFR.

6- Use the AWS Well-Architected Tool (AWS WA Tool)

Using the AWS WA tool will enable you to track questions, take notes, create different milestones, understand the question’s context, understand the best practice being validated, and explore additional resources for the best practice in question in blogs, re:Invent talks, or documentation. Using this tool also helps you to create a custom lens.

7- Maximize time

WAFR should be short and should be completed in hours, not days. To keep the review process concise, it’s important to maintain a balance between asking follow up questions to validate best practices, and to remain within the question context without spending too much time on deep technical discussions. You should also avoid going deep into technical discussions during the review. Instead, take notes, and follow up on this topic as part of the next phase of the review.

8- Maybe is No

In some cases, the team will not be sure if a best practice is implemented or not. In this case, you need to consider the best practices not implemented and document that in the notes in the WA Tool. This way, you can include the solution (or more validation) as a follow up as part of the next phase.

9- Scale and automate as necessary

For large organizations with many workloads, consider building automated and scalable processes to review workloads, identify risks, and remediate them.

Join hands with Cloud Wizard to revamp your Cloud infrastructure with AWS Well-Architected Framework

The AWS Well-Architected Framework has helped businesses enhance their operations and aim for optimal performance. Teaming up with a Select Tier Services Partner like Cloud Wizard can help you get an AWS Well-Architected Review to properly analyze and troubleshoot your cloud infrastructure. Get invaluable guidance on the areas where your cloud practices could improve for better efficiency and workflow while being environmentally sustainable at the same time.

Earn $5,000 in AWS service credits per workload if you implement the review recommendations!

Want to make sure your cloud infrastructure is optimal and operationally up to the mark? Get an AWS Well-Architected Review right away!