## Introduction The AWS Well-Architected Framework is a guide for building and iterating on cloud systems by measuring your architecture against best practices and identifying areas for improvement. ## The Pillars - [[Pillars of the AWS Well-Architected Framework]] ## Key Definitions - [[Component (AWS)]] - [[Workload (AWS)]] - [[Architecture (AWS)]] - [[Milestones (AWS)]] - [[Technology Portfolio (AWS)]] - [[Level Of Effort (AWS)]] ## Roles - Technical Architect (infrastructure) - Solutions Architect (software) - Data Architect - Networking Architect - Security Architect ## Value of Decentralization [TOGAF](https://pubs.opengroup.org/architecture/togaf9-doc/arch/) and [Zachman Framework](https://zachman-feac.com/zachman/about-the-zachman-framework) enterprise architecture leads to a centralized technology architecture team whereas AWS prefers distributed capabilities enforced by _practices_ (processes, standards and norms) and _mechanisms_ (checks, often automated) so that each team has the capability to create best-practices architectures for the customer. ## Design Principles - Stop guessing your capacity needs - Test systems at production scale - Automate with architectural experimentation in mind - Consider evolutionary architectures - Drive architectures using data - Improve through game days that simulate events in production ## References [AWS Docs](https://docs.aws.amazon.com/wellarchitected/latest/framework/welcome.html)