-
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
Create support plans for production workloads
Creating Support Plans for Production Workloads
Creating comprehensive support plans for production workloads is crucial to ensure that all software and services your workload relies on are fully supported. By selecting the right support level, documenting the necessary information, and keeping points of contact updated, teams can quickly resolve service disruptions and software issues, minimizing downtime and maintaining service quality.
Enable Support for All Dependencies
Enable support for all software and services that your production workload depends on. Ensure that support plans are in place for cloud services, third-party software, and any other critical dependencies. By enabling support, teams can address issues more effectively and receive the assistance needed to maintain workload stability.
Select an Appropriate Support Level
Choose the appropriate support level to meet the service-level needs of your production workload. This includes considering factors such as response time, availability of technical support, and support hours. For mission-critical workloads, it may be necessary to have 24/7 support to minimize the impact of any incidents on end users. Selecting the correct support level helps ensure that you have the right support coverage when it matters most.
Document Support Plans and Procedures
Document support plans for each software or service dependency, including how to request support, escalation procedures, and relevant points of contact. This documentation should be readily accessible so that team members know exactly who to contact and how to initiate support during an incident. Detailed support plans minimize confusion during critical incidents and streamline the process of obtaining help.
Verify Contact Information Regularly
Implement mechanisms to ensure that support points of contact are kept up to date. Contact information for vendors and support providers should be verified regularly to ensure it is accurate and accessible. Having correct and up-to-date contact information reduces delays in reaching support teams during service disruptions.
Plan for Service Disruptions
Create contingency plans for service disruptions involving your dependencies. Support plans should include steps for addressing potential failures, backup procedures, and information on alternative resources if a critical dependency is unavailable. Planning for disruptions ensures that your team can respond quickly and maintain service levels even in the event of failures.
Supporting Questions
- How do you ensure that all dependencies of your production workload are adequately supported?
- What support levels are in place for each service or software your workload relies on?
- How is contact information for support providers kept current and easily accessible?
Roles and Responsibilities
Support Coordinator
Responsibilities:
- Enable support plans for all software and services critical to the production workload.
- Maintain documentation of support procedures, including contacts and escalation paths for each dependency.
Operations Manager
Responsibilities:
- Select appropriate support levels for each dependency based on service-level requirements and the criticality of the workload.
- Verify that all support points of contact are accurate and up to date, ensuring that support is available when needed.
Incident Responder
Responsibilities:
- Use documented support plans during incidents to initiate support requests and escalate issues as needed.
- Communicate with support vendors and ensure that any ongoing issues are resolved promptly to minimize impact.
Artifacts
- Support Plan Document: A detailed document for each service or software dependency, outlining how to request support, escalation procedures, and points of contact.
- Contact Information Log: A log of contact information for all support providers, including vendor support details and internal escalation points.
- Contingency Plan for Service Disruptions: A plan that outlines steps for responding to service disruptions, including backup resources and failover procedures.
Relevant AWS Tools
Support and Monitoring Tools
- AWS Support Plans: Choose from different AWS Support Plans (Basic, Developer, Business, or Enterprise) to meet your workload requirements and provide the appropriate support level.
- AWS Trusted Advisor: Provides guidance to help you optimize your workload and receive recommendations on how to best utilize AWS support services.
Incident Management Tools
- AWS Systems Manager Incident Manager: Manages incidents by providing structured playbooks and runbooks, and allows integration with support providers to streamline resolution.
- Amazon CloudWatch: Monitors production workloads, providing data that can be used to inform support providers of issues during a service disruption.
Collaboration and Documentation Tools
- AWS Systems Manager OpsCenter: Integrates with AWS services to manage operational issues, providing a single view of incidents and the ability to contact support.
- Amazon WorkDocs: Stores and manages documentation related to support plans, making it easy for team members to access support procedures and contact information.