--- name: aws-waf-operational-excellence metadata: category: WellArchitectedFramework description: >- Generates guidance for operating AWS workloads, based on the Operational Excellence pillar of the AWS Well-Architected Framework. Use when designing teams, observability, deployment, runbooks or continuous improvement for an AWS workload. --- # AWS Well-Architected Framework skill for the Operational Excellence pillar ## Overview The Operational Excellence pillar is a commitment to building software correctly while consistently delivering a great customer experience. It covers how teams are organized, how a workload is designed and prepared, how it is run at scale, and how it evolves. ## Core principles The recommendations below follow the published framework. Written for this agent from AWS's published Well-Architected Framework. Question codes are AWS's. - **Organize teams around business outcomes**: Tie structure and priorities to what the business needs. Grounding document: https://docs.aws.amazon.com/wellarchitected/latest/framework/oe-design-principles.html - **Implement observability for actionable insights**: Understand behaviour, performance and health well enough to act. Grounding document: https://docs.aws.amazon.com/wellarchitected/latest/framework/oe-design-principles.html - **Safely automate where possible**: Define operations as code, with guardrails. Grounding document: https://docs.aws.amazon.com/wellarchitected/latest/framework/oe-design-principles.html - **Make frequent, small, reversible changes**: Limit the impact of each change, and keep rollback simple. Grounding document: https://docs.aws.amazon.com/wellarchitected/latest/framework/oe-design-principles.html - **Refine operations procedures frequently**: Improve runbooks as the workload changes, and rehearse them. Grounding document: https://docs.aws.amazon.com/wellarchitected/latest/framework/oe-design-principles.html - **Anticipate failure**: Identify and test failure scenarios before they occur. Grounding document: https://docs.aws.amazon.com/wellarchitected/latest/framework/oe-design-principles.html - **Learn from all operational events and metrics**: Share what is learned across teams. Grounding document: https://docs.aws.amazon.com/wellarchitected/latest/framework/oe-design-principles.html - **Use managed services**: Reduce operational burden. Grounding document: https://docs.aws.amazon.com/wellarchitected/latest/framework/oe-design-principles.html ## Relevant products The following are _examples_ of products relevant to this pillar: - **Delivery**: AWS CodePipeline, AWS CodeBuild, AWS CodeDeploy - **Infrastructure as code**: Terraform, AWS CloudFormation, AWS CDK - **Observability**: Amazon CloudWatch, AWS X-Ray, Amazon Managed Grafana - **Operations**: AWS Systems Manager, AWS Config, AWS Health Dashboard ## Workload assessment questions Ask appropriate questions to understand the requirements and constraints of the workload and the organization. Choose from this list: - OPS 1: How do you determine what your priorities are? - OPS 2: How do you structure your organization to support your business outcomes? - OPS 3: How does your organizational culture support your business outcomes? - OPS 4: How do you implement observability in your workload? - OPS 5: How do you reduce defects, ease remediation, and improve flow into production? - OPS 6: How do you mitigate deployment risks? - OPS 7: How do you know that you are ready to support a workload? - OPS 8: How do you utilize workload observability in your organization? - OPS 9: How do you understand the health of your operations? - OPS 10: How do you manage workload and operations events? - OPS 11: How do you evolve operations? ## Validation checklist Use this checklist to evaluate the architecture against this pillar: - Business priorities and workload ownership are stated. - All infrastructure is deployed from code in source control. - Pipelines test changes, and changes are small and reversible. - Application, infrastructure and business metrics are collected. - Alarms lead to runbooks with named responders. - Operational readiness is reviewed before launch. - Events are reviewed and lessons are acted on.