Search for Well Architected Advice
-
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
-
- Have a process for continuous improvement
- Perform post-incident analysis
- Implement feedback loops
- Perform knowledge management
- Define drivers for improvement
- Validate insights
- Perform operations metrics reviews
- Document and share lessons learned
- Allocate time to make improvements
- Perform post-incident analysis
-
Security
-
- Separate workloads using accounts
- Secure account root user and properties
- Identify and validate control objectives
- Keep up-to-date with security recommendations
- Keep up-to-date with security threats
- Identify and prioritize risks using a threat model
- Automate testing and validation of security controls in pipelines
- Evaluate and implement new security services and features regularly
-
- Define access requirements
- Grant least privilege access
- Define permission guardrails for your organization
- Manage access based on life cycle
- Establish emergency access process
- Share resources securely within your organization
- Reduce permissions continuously
- Share resources securely with a third party
- Analyze public and cross-account access
-
- Perform regular penetration testing
- Deploy software programmatically
- Regularly assess security properties of the pipelines
- Train for Application Security
- Automate testing throughout the development and release lifecycle
- Manual Code Reviews
- Centralize services for packages and dependencies
- Build a program that embeds security ownership in workload teams
-
-
Reliability
-
- Be aware of service quotas and constraints in Cloud Services
- Manage service quotas across accounts and Regions
- Accommodate fixed service quotas and constraints through architecture
- Monitor and manage quotas
- Automate quota management
- Ensure sufficient gap between quotas and usage to accommodate failover
-
- Use highly available network connectivity for your workload public endpoints
- Provision Redundant Connectivity Between Private Networks in the Cloud and On-Premises Environments
- Ensure IP subnet allocation accounts for expansion and availability
- Prefer hub-and-spoke topologies over many-to-many mesh
- Enforce non-overlapping private IP address ranges in all private address spaces where they are connected
-
- 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
- Define and calculate metrics
- Send notifications
- Automate responses
-
- 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
-
- Scale workload infrastructure dynamically
- 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
- Implement a data classification policy
- Remove unneeded or redundant data
-
- Articles coming soon
< All Topics
Print
Monitor all components of the workload to detect failures
PostedDecember 20, 2024
UpdatedMarch 22, 2025
ByKevin McCaffrey
ID: REL_REL11_1
Monitoring is critical for maintaining workload resilience. By constantly assessing the health of each component, organizations can detect issues early, ensuring minimal disruptions and enabling swift recovery, thus supporting high availability and reducing mean time to recovery (MTTR).
Best Practices
Implement Comprehensive Monitoring Solutions
- Utilize AWS services like Amazon CloudWatch for real-time monitoring of your applications and resources. Set up alarms and dashboards to track metrics that reflect the health and performance of your workloads.
- Integrate third-party monitoring tools if needed, to enhance visibility, especially for applications spanning multiple cloud environments or hybrid setups.
- Define key performance indicators (KPIs) relevant to your business objectives, ensuring that your monitoring setup prioritizes critical application components and user impact.
- Establish rigorous logging practices across all components, enabling you to capture detailed information during failures for root cause analysis and ongoing improvement.
- Regularly review and adjust monitoring thresholds and alarms based on evolving workload demands and prior incidents to ensure continued effectiveness.
Questions to ask your team
- What monitoring tools are currently in place to track the performance of your workload components?
- How frequently do you review the health metrics of your workload?
- What key performance indicators (KPIs) are being monitored to ensure your workload is operating optimally?
- How are you alerted when a failure or degradation is detected in your workload?
- What processes are in place for automated responses to component failures?
- Have you conducted any drills or tests to verify the effectiveness of your monitoring systems?
Who should be doing this?
Cloud Architect
- Design resilient architectures that incorporate monitoring capabilities.
- Define key performance indicators (KPIs) relevant to the workload’s business value.
- Implement strategies for high availability and automated recovery in the architecture.
DevOps Engineer
- Set up monitoring tools to track the health of all components of the workload.
- Automate alerts for failures or performance degradations.
- Collaborate with the cloud architect to ensure alignment on monitoring strategies.
Site Reliability Engineer (SRE)
- Continuously monitor system performance and reliability.
- Analyze incidents to identify root causes and improve monitoring practices.
- Maintain documentation for monitoring processes and ensure they are up to date.
Product Owner
- Define business value metrics that inform the monitoring strategy.
- Prioritize features and fixes that enhance reliability based on monitoring data.
- Communicate the importance of reliability and monitoring to stakeholders.
What evidence shows this is happening in your organization?
- System Health Monitoring Dashboard: A real-time dashboard displaying the health status and key performance indicators (KPIs) of all workload components. It includes alerts for failures and degradations, enabling quick response and resolution.
- Incident Response Playbook: A structured playbook outlining the steps to take when a component failure is detected. This document includes identifying responsible teams, escalation paths, and recovery procedures to minimize downtime.
- Monitoring and Alerting Policy: A formal policy defining monitoring requirements for all workload components. It specifies which KPIs to monitor, appropriate thresholds for alerts, and procedures for escalation when issues are detected.
- Monthly Reliability Report: A comprehensive report summarizing the performance and reliability of the workload over the past month. It details incidents, recovery times, and trends in failures to guide future improvements and optimizations.
- Checklist for Monitoring Implementation: A detailed checklist to ensure that all components of the workload are monitored properly. This checklist includes tasks such as configuring metrics, setting up alerts, and testing automated response mechanisms.
Cloud Services
AWS
- Amazon CloudWatch: A monitoring service for AWS cloud resources and applications that provides data and actionable insights to monitor performance and resource utilization.
- AWS X-Ray: Helps developers analyze and debug production applications, providing insights into application performance and monitoring requests.
- AWS CloudTrail: Enables governance, compliance, and operational and risk auditing of your AWS account by logging API calls made on your account.
Azure
- Azure Monitor: Provides full-stack monitoring for applications, infrastructure, and network, enabling proactive measures based on insights.
- Azure Application Insights: A feature of Azure Monitor that provides powerful analytics tools to help you diagnose issues and understand what users actually do with your apps.
- Azure Log Analytics: Collects and analyzes log data from various sources, providing operational insights for your applications and infrastructure.
Google Cloud Platform
- Google Cloud Monitoring: Monitoring service that provides visibility into your applications and resources, allowing you to set up custom metrics and alerts.
- Google Cloud Logging: A service that allows you to store, search, analyze, and alert on log data from your applications and services on Google Cloud.
- Stackdriver Error Reporting: A service that displays and allows you to filter errors from your applications, helping in identifying and resolving issues quickly.
Table of Contents