-
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
Mechanisms exist to identify responsibility and ownership
Establishing Mechanisms to Identify Responsibility and Ownership
To ensure seamless operations, it is crucial to have mechanisms in place that identify responsibility and ownership for tasks. When ownership is not clearly assigned, having defined escalation paths helps ensure that responsibilities are promptly assigned, and needs are addressed effectively.
Define Escalation Paths for Unassigned Tasks
Establish defined escalation paths for situations where no individual or team is identified as responsible for specific tasks. This helps to ensure that unassigned responsibilities are addressed without delay. Escalation paths direct unassigned tasks to someone with the authority to assign ownership or initiate planning to address those responsibilities.
Assign Authority for Task Ownership
Assign individuals with the authority to determine responsibility for unassigned tasks. This ensures that ownership is quickly assigned and that tasks do not remain unattended. This can involve managers, team leads, or designated escalation officers, depending on the organization’s structure.
Implement Escalation Mechanisms
Implement mechanisms that facilitate the escalation process, such as incident tracking tools, escalation workflows, or other automated systems. These mechanisms help in tracking tasks and ensuring that unassigned responsibilities are brought to the attention of those in charge of assigning ownership. Automation helps make the escalation process efficient and reduces potential delays.
Ensure Clear Communication of Escalation Paths
Ensure that all team members understand the escalation paths and know how to initiate the escalation process if they identify unassigned tasks. Effective communication of these paths helps avoid confusion and ensures that everyone knows the steps to take if they encounter an issue with ownership.
Supporting Questions
- What escalation paths are in place for unassigned responsibilities?
- Who has the authority to assign ownership to tasks that do not have an identified owner?
- How are team members informed about the process for escalating unassigned responsibilities?
Roles and Responsibilities
Escalation Officer
Responsibilities:
- Act as the point of contact for unassigned responsibilities.
- Assign ownership to appropriate individuals or teams when tasks are escalated.
Team Member
Responsibilities:
- Identify tasks or responsibilities without a defined owner and initiate escalation.
- Follow defined escalation paths when responsibilities are not clear.
Manager
Responsibilities:
- Communicate escalation paths to team members.
- Ensure that responsibilities are assigned promptly when escalated.
Artifacts
- Escalation Path Documentation: A document detailing the escalation paths and the authorities involved in assigning ownership.
- Unassigned Task Log: A log that tracks tasks that have been escalated due to unassigned ownership and their resolution.
- Ownership Assignment Record: A record of ownership assignments following escalation, including assigned owners and dates.
Relevant AWS Tools
Escalation and Incident Tracking Tools
- AWS Systems Manager Incident Manager: Helps automate incident escalation, track unassigned responsibilities, and ensure prompt assignment to the right individuals.
- AWS Lambda: Automates escalation workflows by executing functions that can notify responsible personnel or assign tasks when unassigned responsibilities are detected.
Task Assignment and Authority Tools
- AWS Identity and Access Management (IAM): Defines roles and permissions, helping to assign appropriate authority for decision-making and ownership assignment.
- Amazon SNS (Simple Notification Service): Facilitates communication during the escalation process, notifying relevant stakeholders about unassigned responsibilities that need addressing.
Communication Tools
- Amazon Chime: Supports team meetings for discussing escalation paths and resolving unassigned responsibilities.
- AWS WorkDocs: Stores and shares documentation related to escalation paths, ensuring all team members have access to up-to-date information.