Use templated answers to perform Well-Architected reviews at scale

{"value":"For larger customers, performing [AWS Well-Architected (AWS WA) Framework](https://aws.amazon.com/architecture/well-architected/) reviews often involves a combination of different teams. Coordinating participants from each team in order to perform a review increases the time taken and is expensive. In a large organization, there are often hundreds of AWS accounts where teams can store review documents, which means there is no way to quickly identify risks or spot common issues or trends that could influence improvements.\n\nTo address this, we created a solution to help you perform reviews easier and faster. It allows workload owners to automatically populate their reviews with templated answers to questions in the [AWS Well-Architected Tool (AWS WA Tool)](https://aws.amazon.com/well-architected-tool/). These answers may be a shared responsibility between an application team and a centralized team such as platform, security, or finance. This way, application teams have fewer questions to answer and centralized team members have fewer reviews to attend, because answers that are common to all workloads are pre-populated in workload reviews. The solution also provides centralized reporting to provide a centralized view of AWS WA reviews conducted across the organization.\n\n\n#### **Perform Well-Architected reviews at scale**\n\n\nIn large organizations, responsibilities are often distributed across multiple teams, for example:\n\n- A platform team manages an [AWS Control Tower](https://docs.aws.amazon.com/controltower/?id=docs_gateway) [landing zone](https://aws.amazon.com/controltower/features/) and provides accounts, access controls, and networking.\n- A security team defines security policies for this solution and enforces them using guardrails or marketplace solutions.\n- A financial operations team mandates a tagging policy to allow for accurate cost cross-charging within the business.\n- Application teams developing internal or external facing applications use a shared platform provided by a Cloud Center of Excellence.\n\nTo perform a traditional AWS WA review for this example, you would likely need to invite representatives from each of these teams to attend the review. This is because one team would be unlikely to be able to answer the foundational questions alone.\n\nWith tens or hundreds of workloads being reviewed every year, this approach doesn’t scale. This is because representatives from central teams end up attending every review. With more people involved, scheduling reviews is difficult, the overall time required to conduct the review increases, and longer reviews with more people are more expensive to perform.\n\nAdditionally, the review document is usually created and stored in one of the application team’s AWS accounts. In a large organization, there are often hundreds of AWS accounts. This makes it difficult for leadership to get a consolidated view of the risks identified across the reviews. It also makes it almost impossible to spot common issues or trends that could influence roadmaps for organization-wide improvements.\n\n\n#### **Automatically populate templated answers for quicker, easier reviews**\n\n\nOur solution allows you to address these challenges by using the AWS WA Tool to create answer templates. An answer template looks like a regular AWS WA Tool workload review. However, these answers propagate automatically to application workload reviews and are visible by application workload owners during the review process. This way, where there is a shared responsibility, workload owners can see this detail and they can be confident that the inputs provided by the central teams are correct and consistent.\n\nThe solution operates as shown in Figure 1 and works as follows:\n\n1. Central teams use the AWS WA Tool in the “central” AWS account to create workload templates. These are prefixed with “CentralTemplate” (or by a [stack parameter](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/cfn-using-console-create-stack-parameters.html)).\n2. The central team answers the questions they’re responsible for and marks all others as “Question does not apply to this workload”.\n3. When an application team is ready to perform an AWS WA Framework review, they create a new workload in their workload account in the AWS WA Tool.\n4. This new workload is then shared with the central account (with contributor access) by an [AWS Lambda](http://aws.amazon.com/lambda) function. After that, a message is placed on an [Amazon Simple Notification Service (Amazon SNS)](http://aws.amazon.com/sns) topic in the central account.\n5. In the central account, a Lambda function is subscribed to the Amazon SNS topic from step 4. This function accepts the incoming share, then shares all templates back to the workload account (with read-only access).\n6. The shared workload is then populated with templated answers from templates with the “CentralTemplate” prefix. Both the selected choices and notes are written to the shared workload. Questions in the template marked as “question does not apply to this workload” are ignored.\n7. As the application team proceeds through the questions, they will see the pre-populated answers from the template.\n8. Should a central team need to update their answers, they can update their template and [create a milestone](https://docs.aws.amazon.com/wellarchitected/latest/userguide/milestones.html).\n9. The milestone creation invokes an [AWS Step Functions](http://aws.amazon.com/step-functions) workflow. The workflow collects all shared workload IDs. Next, it uses a [map state](https://docs.aws.amazon.com/step-functions/latest/dg/amazon-states-language-map-state.html) to fan-out the updating of all shared workloads. Whether this process should overwrite or append workload answers is configurable at deployment time.\n10. Because all workloads are now visible in the central account, the dashboards referenced in AWS WA labs can be used for consolidated analysis of risks.\n\n\n\nFigure 1. Solution components and workflow steps\n\nThe solution can be coupled with an [Amazon QuickSight](https://aws.amazon.com/quicksight) powered [reporting solution](https://wellarchitectedlabs.com/well-architectedtool/300_labs/300_building_custom_aws_well-architected_reports_with_amazon_athena_and_amazon_quicksight/) to get an organization-wide view of reviews from a single account. These reviews can also be shared with your AWS account team for ongoing collaborative improvement.\n\n*Note*: For some workloads, you may need additional AWS WA Framework [lenses](https://docs.aws.amazon.com/wellarchitected/latest/userguide/lenses.html). The solution offered in this post is lens agnostic, and also supports the use of [custom lenses](https://docs.aws.amazon.com/wellarchitected/latest/userguide/lenses-custom.html). To deploy the solution, refer to the deployment instructions which can be found on GitHub under [aws-samples](https://github.com/aws-samples/aws-well-architected-tool-template-automation).\n\n\n#### **Conclusion**\n\n\nIn this post, we explored some of the challenges faced by large enterprises when performing AWS WA Framework reviews at scale and showed you a solution to help your teams define templated answers to particular questions in the AWS WA Tool.\n\nYou can deploy this solution to your AWS accounts today by following the deployment instructions included on the [aws-samples](https://github.com/aws-samples/aws-well-architected-tool-template-automation) repository.\n\nHaving these templated answers automatically propagated to application workload reviews reduces the number of questions application teams have to answer, as well as the number of attendees required for a review. With this solution, all the AWS WA Framework reviews can be viewed in a single AWS account, so you can also apply the [reporting solution provided in AWS WA labs](https://wellarchitectedlabs.com/well-architectedtool/300_labs/300_building_custom_aws_well-architected_reports_with_amazon_athena_and_amazon_quicksight/) to run centralized reports against all AWS WA Framework reviews in your organization.\n\n\n#### **Looking for more architecture content?**\n\n\n[AWS Architecture Center](https://aws.amazon.com/architecture/) provides reference architecture diagrams, vetted architecture solutions, [Well-Architected](https://aws.amazon.com/architecture/well-architected/) best practices, patterns, icons, and more!\n\n\n\n\n#### **Thomas Attree**\n\n\nThomas is a Solutions Architect at Amazon Web Services based in London. Thomas currently helps customers in the power and utilities industry and applies his passion for sustainability to help customers architect applications for energy efficiency.\n\n\n\n\n#### **Paul Le Page**\n\n\nPaul Le Page is a Senior Solutions Architect at AWS. He works with enterprise retail customers, helping them with migrations to the cloud and adoption of cloud native services. In his free time, Paul enjoys travel, food and the great outdoors.","render":"<p>For larger customers, performing <a href=\"https://aws.amazon.com/architecture/well-architected/\" target=\"_blank\">AWS Well-Architected (AWS WA) Framework</a> reviews often involves a combination of different teams. Coordinating participants from each team in order to perform a review increases the time taken and is expensive. In a large organization, there are often hundreds of AWS accounts where teams can store review documents, which means there is no way to quickly identify risks or spot common issues or trends that could influence improvements.</p>\n<p>To address this, we created a solution to help you perform reviews easier and faster. It allows workload owners to automatically populate their reviews with templated answers to questions in the <a href=\"https://aws.amazon.com/well-architected-tool/\" target=\"_blank\">AWS Well-Architected Tool (AWS WA Tool)</a>. These answers may be a shared responsibility between an application team and a centralized team such as platform, security, or finance. This way, application teams have fewer questions to answer and centralized team members have fewer reviews to attend, because answers that are common to all workloads are pre-populated in workload reviews. The solution also provides centralized reporting to provide a centralized view of AWS WA reviews conducted across the organization.</p>\n<h4><a id=\"Perform_WellArchitected_reviews_at_scale_5\"></a><strong>Perform Well-Architected reviews at scale</strong></h4>\n<p>In large organizations, responsibilities are often distributed across multiple teams, for example:</p>\n<ul>\n<li>A platform team manages an <a href=\"https://docs.aws.amazon.com/controltower/?id=docs_gateway\" target=\"_blank\">AWS Control Tower</a> <a href=\"https://aws.amazon.com/controltower/features/\" target=\"_blank\">landing zone</a> and provides accounts, access controls, and networking.</li>\n<li>A security team defines security policies for this solution and enforces them using guardrails or marketplace solutions.</li>\n<li>A financial operations team mandates a tagging policy to allow for accurate cost cross-charging within the business.</li>\n<li>Application teams developing internal or external facing applications use a shared platform provided by a Cloud Center of Excellence.</li>\n</ul>\n<p>To perform a traditional AWS WA review for this example, you would likely need to invite representatives from each of these teams to attend the review. This is because one team would be unlikely to be able to answer the foundational questions alone.</p>\n<p>With tens or hundreds of workloads being reviewed every year, this approach doesn’t scale. This is because representatives from central teams end up attending every review. With more people involved, scheduling reviews is difficult, the overall time required to conduct the review increases, and longer reviews with more people are more expensive to perform.</p>\n<p>Additionally, the review document is usually created and stored in one of the application team’s AWS accounts. In a large organization, there are often hundreds of AWS accounts. This makes it difficult for leadership to get a consolidated view of the risks identified across the reviews. It also makes it almost impossible to spot common issues or trends that could influence roadmaps for organization-wide improvements.</p>\n<h4><a id=\"Automatically_populate_templated_answers_for_quicker_easier_reviews_22\"></a><strong>Automatically populate templated answers for quicker, easier reviews</strong></h4>\n<p>Our solution allows you to address these challenges by using the AWS WA Tool to create answer templates. An answer template looks like a regular AWS WA Tool workload review. However, these answers propagate automatically to application workload reviews and are visible by application workload owners during the review process. This way, where there is a shared responsibility, workload owners can see this detail and they can be confident that the inputs provided by the central teams are correct and consistent.</p>\n<p>The solution operates as shown in Figure 1 and works as follows:</p>\n<ol>\n<li>Central teams use the AWS WA Tool in the “central” AWS account to create workload templates. These are prefixed with “CentralTemplate” (or by a <a href=\"https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/cfn-using-console-create-stack-parameters.html\" target=\"_blank\">stack parameter</a>).</li>\n<li>The central team answers the questions they’re responsible for and marks all others as “Question does not apply to this workload”.</li>\n<li>When an application team is ready to perform an AWS WA Framework review, they create a new workload in their workload account in the AWS WA Tool.</li>\n<li>This new workload is then shared with the central account (with contributor access) by an <a href=\"http://aws.amazon.com/lambda\" target=\"_blank\">AWS Lambda</a> function. After that, a message is placed on an <a href=\"http://aws.amazon.com/sns\" target=\"_blank\">Amazon Simple Notification Service (Amazon SNS)</a> topic in the central account.</li>\n<li>In the central account, a Lambda function is subscribed to the Amazon SNS topic from step 4. This function accepts the incoming share, then shares all templates back to the workload account (with read-only access).</li>\n<li>The shared workload is then populated with templated answers from templates with the “CentralTemplate” prefix. Both the selected choices and notes are written to the shared workload. Questions in the template marked as “question does not apply to this workload” are ignored.</li>\n<li>As the application team proceeds through the questions, they will see the pre-populated answers from the template.</li>\n<li>Should a central team need to update their answers, they can update their template and <a href=\"https://docs.aws.amazon.com/wellarchitected/latest/userguide/milestones.html\" target=\"_blank\">create a milestone</a>.</li>\n<li>The milestone creation invokes an <a href=\"http://aws.amazon.com/step-functions\" target=\"_blank\">AWS Step Functions</a> workflow. The workflow collects all shared workload IDs. Next, it uses a <a href=\"https://docs.aws.amazon.com/step-functions/latest/dg/amazon-states-language-map-state.html\" target=\"_blank\">map state</a> to fan-out the updating of all shared workloads. Whether this process should overwrite or append workload answers is configurable at deployment time.</li>\n<li>Because all workloads are now visible in the central account, the dashboards referenced in AWS WA labs can be used for consolidated analysis of risks.</li>\n</ol>\n<p><img src=\"https://dev-media.amazoncloud.cn/cc46da91972e4833b8f9fa8e40742b51_image.png\" alt=\"image.png\" /></p>\n<p>Figure 1. Solution components and workflow steps</p>\n<p>The solution can be coupled with an <a href=\"https://aws.amazon.com/quicksight\" target=\"_blank\">Amazon QuickSight</a> powered <a href=\"https://wellarchitectedlabs.com/well-architectedtool/300_labs/300_building_custom_aws_well-architected_reports_with_amazon_athena_and_amazon_quicksight/\" target=\"_blank\">reporting solution</a> to get an organization-wide view of reviews from a single account. These reviews can also be shared with your AWS account team for ongoing collaborative improvement.</p>\n<p><em>Note</em>: For some workloads, you may need additional AWS WA Framework <a href=\"https://docs.aws.amazon.com/wellarchitected/latest/userguide/lenses.html\" target=\"_blank\">lenses</a>. The solution offered in this post is lens agnostic, and also supports the use of <a href=\"https://docs.aws.amazon.com/wellarchitected/latest/userguide/lenses-custom.html\" target=\"_blank\">custom lenses</a>. To deploy the solution, refer to the deployment instructions which can be found on GitHub under <a href=\"https://github.com/aws-samples/aws-well-architected-tool-template-automation\" target=\"_blank\">aws-samples</a>.</p>\n<h4><a id=\"Conclusion_49\"></a><strong>Conclusion</strong></h4>\n<p>In this post, we explored some of the challenges faced by large enterprises when performing AWS WA Framework reviews at scale and showed you a solution to help your teams define templated answers to particular questions in the AWS WA Tool.</p>\n<p>You can deploy this solution to your AWS accounts today by following the deployment instructions included on the <a href=\"https://github.com/aws-samples/aws-well-architected-tool-template-automation\" target=\"_blank\">aws-samples</a> repository.</p>\n<p>Having these templated answers automatically propagated to application workload reviews reduces the number of questions application teams have to answer, as well as the number of attendees required for a review. With this solution, all the AWS WA Framework reviews can be viewed in a single AWS account, so you can also apply the <a href=\"https://wellarchitectedlabs.com/well-architectedtool/300_labs/300_building_custom_aws_well-architected_reports_with_amazon_athena_and_amazon_quicksight/\" target=\"_blank\">reporting solution provided in AWS WA labs</a> to run centralized reports against all AWS WA Framework reviews in your organization.</p>\n<h4><a id=\"Looking_for_more_architecture_content_59\"></a><strong>Looking for more architecture content?</strong></h4>\n<p><a href=\"https://aws.amazon.com/architecture/\" target=\"_blank\">AWS Architecture Center</a> provides reference architecture diagrams, vetted architecture solutions, <a href=\"https://aws.amazon.com/architecture/well-architected/\" target=\"_blank\">Well-Architected</a> best practices, patterns, icons, and more!</p>\n<p><img src=\"https://dev-media.amazoncloud.cn/4481bc45fe09400187501dba4f4eefe1_image.png\" alt=\"image.png\" /></p>\n<h4><a id=\"Thomas_Attree_67\"></a><strong>Thomas Attree</strong></h4>\n<p>Thomas is a Solutions Architect at Amazon Web Services based in London. Thomas currently helps customers in the power and utilities industry and applies his passion for sustainability to help customers architect applications for energy efficiency.</p>\n<p><img src=\"https://dev-media.amazoncloud.cn/4d6b07371ab84aef8fd8d236449ded4d_image.png\" alt=\"image.png\" /></p>\n<h4><a id=\"Paul_Le_Page_75\"></a><strong>Paul Le Page</strong></h4>\n<p>Paul Le Page is a Senior Solutions Architect at AWS. He works with enterprise retail customers, helping them with migrations to the cloud and adoption of cloud native services. In his free time, Paul enjoys travel, food and the great outdoors.</p>\n"}