-
Operational Excellence
-
- Resources have identified owners
- Processes and procedures have identified owners
- Operations activities have identified owners responsible for their performance
- Team members know what they are responsible for
- Mechanisms exist to identify responsibility and ownership
- Mechanisms exist to request additions, changes, and exceptions
- Responsibilities between teams are predefined or negotiated
-
- Executive Sponsorship
- Team members are empowered to take action when outcomes are at risk
- Escalation is encouraged
- Communications are timely, clear, and actionable
- Experimentation is encouraged
- Team members are encouraged to maintain and grow their skill sets
- Resource teams appropriately
- Diverse opinions are encouraged and sought within and across teams
-
- Use version control
- Test and validate changes
- Use configuration management systems
- Use build and deployment management systems
- Perform patch management
- Implement practices to improve code quality
- Share design standards
- Use multiple environments
- Make frequent, small, reversible changes
- Fully automate integration and deployment
-
Security
-
- Evaluate and implement new security services and features regularly
- Automate testing and validation of security controls in pipelines
- Identify and prioritize risks using a threat model
- Keep up-to-date with security recommendations
- Keep up-to-date with security threats
- Identify and validate control objectives
- Secure account root user and properties
- Separate workloads using accounts
-
- Analyze public and cross-account access
- Manage access based on life cycle
- Share resources securely with a third party
- Reduce permissions continuously
- Share resources securely within your organization
- Establish emergency access process
- Define permission guardrails for your organization
- Grant least privilege access
- Define access requirements
-
- Build a program that embeds security ownership in workload teams
- Centralize services for packages and dependencies
- Manual code reviews
- Automate testing throughout the development and release lifecycle
- Train for application security
- Regularly assess security properties of the pipelines
- Deploy software programmatically
- Perform regular penetration testing
-
-
Reliability
-
- How do you ensure sufficient gap between quotas and maximum usage to accommodate failover?
- How do you automate quota management?
- How do you monitor and manage service quotas?
- How do you accommodate fixed service quotas and constraints through architecture?
- How do you manage service quotas and constraints across accounts and Regions?
- How do you manage service quotas and constraints?
- How do you build a program that embeds reliability into workload teams?
-
- How do you enforce non-overlapping private IP address ranges in all private address spaces?
- How do you prefer hub-and-spoke topologies over many-to-many mesh?
- How do you ensure IP subnet allocation accounts for expansion and availability?
- How do you provision redundant connectivity between private networks in the cloud and on-premises environments?
- How do you use highly available network connectivity for workload public endpoints?
-
- Monitor end-to-end tracing of requests through your system
- Conduct reviews regularly
- Analytics
- Automate responses (Real-time processing and alarming)
- Send notifications (Real-time processing and alarming)
- Define and calculate metrics (Aggregation)
- Monitor End-to-End Tracing of Requests Through Your System
-
- Monitor all components of the workload to detect failures
- Fail over to healthy resources
- Automate healing on all layers
- Rely on the data plane and not the control plane during recovery
- Use static stability to prevent bimodal behavior
- Send notifications when events impact availability
- Architect your product to meet availability targets and uptime service level agreements (SLAs)
-
-
Cost Optimization
-
- Establish ownership of cost optimization
- Establish a partnership between finance and technology
- Establish cloud budgets and forecasts
- Implement cost awareness in your organizational processes
- Monitor cost proactively
- Keep up-to-date with new service releases
- Quantify business value from cost optimization
- Report and notify on cost optimization
- Create a cost-aware culture
-
- Perform cost analysis for different usage over time
- Analyze all components of this workload
- Perform a thorough analysis of each component
- Select components of this workload to optimize cost in line with organization priorities
- Perform cost analysis for different usage over time
- Select software with cost effective licensing
-
-
Performance
-
- Learn about and understand available cloud services and features
- Evaluate how trade-offs impact customers and architecture efficiency
- Use guidance from your cloud provider or an appropriate partner to learn about architecture patterns and best practices
- Factor cost into architectural decisions
- Use policies and reference architectures
- Use benchmarking to drive architectural decisions
- Use a data-driven approach for architectural choices
-
- Use purpose-built data store that best support your data access and storage requirements
- Collect and record data store performance metrics
- Evaluate available configuration options for data store
- Implement Strategies to Improve Query Performance in Data Store
- Implement data access patterns that utilize caching
-
- Understand how networking impacts performance
- Evaluate available networking features
- Choose appropriate dedicated connectivity or VPN for your workload
- Use load balancing to distribute traffic across multiple resources
- Choose network protocols to improve performance
- Choose your workload's location based on network requirements
- Optimize network configuration based on metrics
-
- Establish key performance indicators (KPIs) to measure workload health and performance
- Use monitoring solutions to understand the areas where performance is most critical
- Define a process to improve workload performance
- Review metrics at regular intervals
- Load test your workload
- Use automation to proactively remediate performance-related issues
- Keep your workload and services up-to-date
-
-
Sustainability
-
- Optimize geographic placement of workloads based on their networking requirements
- Align SLAs with sustainability goals
- Optimize geographic placement of workloads based on their networking requirements
- Stop the creation and maintenance of unused assets
- Optimize team member resources for activities performed
- Implement buffering or throttling to flatten the demand curve
-
- Optimize software and architecture for asynchronous and scheduled jobs
- Remove or refactor workload components with low or no use
- Optimize areas of code that consume the most time or resources
- Optimize impact on devices and equipment
- Use software patterns and architectures that best support data access and storage patterns
- Remove unneeded or redundant data
- Use technologies that support data access and storage patterns
- Use policies to manage the lifecycle of your datasets
- Use shared file systems or storage to access common data
- Back up data only when difficult to recreate
- Use elasticity and automation to expand block storage or file system
- Minimize data movement across networks
-
- Articles coming soon
Ensure a consistent review of operational readiness
Ensuring Consistent Review of Operational Readiness
Operational Readiness Reviews (ORRs) are crucial for validating that a workload can be safely operated in production. ORRs ensure that all processes, people, and systems are ready to maintain and support the workload, reducing the risk of failures or unplanned downtime. By conducting consistent ORRs, teams can certify their workloads for operational stability and identify areas for improvement before deployment.
Conduct Operational Readiness Reviews (ORRs)
Use ORRs to validate that your workload is ready for production. ORRs involve a detailed review and inspection process using a checklist of requirements, covering areas such as monitoring, incident response, backup, and recovery. An ORR helps ensure that all components of the workload are properly configured, maintained, and supported.
Use ORRs for Self-Service Certification
Operational Readiness Reviews are designed to be a self-service experience that teams use to certify their workloads. Teams use a standardized checklist to assess their readiness and ensure that best practices are followed. This empowers teams to take ownership of their workloads and ensure they meet the required standards before going live.
Checklist-Based Validation
ORRs utilize a checklist of requirements to ensure consistency and completeness in evaluating readiness. The checklist includes items such as monitoring capabilities, incident management protocols, security controls, and performance testing. By using a checklist, teams can systematically review all critical aspects of the workload, identify gaps, and implement necessary improvements.
Incorporate Best Practices and Lessons Learned
ORRs incorporate best practices and lessons learned from years of building and operating software at Amazon. These best practices include insights into handling incidents, scaling workloads, securing systems, and maintaining high availability. Using this knowledge, teams can improve their operational processes and be better prepared to handle potential issues.
Validate Safety and Stability
The goal of an ORR is to validate that the workload can be operated safely and reliably. This includes ensuring that all dependencies are functioning correctly, that there are adequate monitoring and alerting mechanisms in place, and that the team is prepared to respond to any incidents. By consistently conducting ORRs, teams can reduce the risk of operational issues and ensure stable workload operation.
Supporting Questions
- What is the process for conducting an Operational Readiness Review (ORR)?
- How does an ORR help validate the safety and stability of your workload?
- What best practices are included in the ORR checklist to ensure operational readiness?
Roles and Responsibilities
Operations Manager
Responsibilities:
- Conduct Operational Readiness Reviews (ORRs) to validate the operational readiness of workloads.
- Ensure that all checklist items are completed and that any identified gaps are addressed before deployment.
DevOps Engineer
Responsibilities:
- Participate in ORRs to verify that all infrastructure components are configured and monitored correctly.
- Ensure that any automation scripts, monitoring tools, or configuration management settings meet the requirements of the ORR checklist.
Service Owner
Responsibilities:
- Take ownership of the workload and ensure that it meets all requirements outlined in the ORR checklist.
- Implement best practices and lessons learned from previous ORRs to improve workload readiness.
Artifacts
- Operational Readiness Checklist: A comprehensive checklist used during ORRs to validate readiness, covering areas such as monitoring, security, incident response, and backup.
- Readiness Review Report: A report summarizing the results of the ORR, including identified gaps, action items, and timelines for remediation.
- Operational Readiness Certification Document: A document certifying that the workload has passed the ORR and is ready for production deployment.
- AWS Operational Readiness Reviews: Read about AWS Operational Readiness Reviews here.
Relevant AWS Tools
Review and Certification Tools
- AWS Well-Architected Tool: Provides best practices and guidance for reviewing workload readiness and helps teams understand potential gaps in their workload architecture.
- AWS Trusted Advisor: Checks the readiness of AWS resources and provides recommendations on security, performance, cost optimization, and fault tolerance, which can be used as part of an ORR.
Monitoring and Alerting Tools
- Amazon CloudWatch: Monitors the health and performance of workloads, providing metrics and alerts to validate operational readiness.
- AWS Systems Manager: Automates compliance checks and operational reviews to validate readiness as part of the ORR process.
Incident Management Tools
- AWS Systems Manager Incident Manager: Supports incident response capabilities, ensuring that teams are ready to respond to issues identified during the ORR.
- AWS Config: Tracks configuration changes and validates that the current configurations meet readiness requirements, helping identify gaps during ORRs.