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
-
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
< All Topics
Print
Identify key performance indicators
PostedNovember 6, 2024
UpdatedNovember 8, 2024
ByKevin McCaffrey
Implementing Observability in Your Workload
Implementing observability in your workload is crucial to understanding its state and making data-driven decisions based on business requirements. Observability allows you to gain insights into the performance, health, and behavior of your workload, enabling proactive response to issues and informed decision-making.
Identify Key Performance Indicators
Start by defining key performance indicators (KPIs) that align with your business requirements. KPIs help ensure that monitoring activities are meaningful and focused on the metrics that are most critical to achieving your objectives. Defining KPIs allows teams to track performance and make adjustments as needed to meet business goals.
Establish Effective Monitoring
Set up effective monitoring that captures relevant metrics for your workload. This includes monitoring metrics such as system health, resource utilization, error rates, and latency. Monitoring provides the data required for observability, enabling teams to understand how well workloads are performing and identify potential issues before they impact customers.
Implement Centralized Logging
Implement centralized logging to gather and store logs from various components of your workload. Logging is essential for troubleshooting and provides valuable insights into workload behavior. By centralizing logs, you make it easier to correlate events and understand how different parts of your system interact.
Use Tracing to Identify Bottlenecks
Use distributed tracing to track the flow of requests through your workload and identify bottlenecks. Tracing allows teams to understand how different services interact, identify latency issues, and uncover the root causes of performance problems. This visibility is critical for optimizing workload performance and ensuring smooth user experiences.
Visualize Data for Better Insights
Use visualization tools to present data in a way that helps teams quickly understand the state of the workload. Dashboards and alerts help summarize key metrics and provide real-time insights into the health and performance of your system. Visualization makes it easier to detect anomalies and prioritize actions based on business impact.
Supporting Questions
- What key performance indicators (KPIs) are defined for monitoring your workload?
- How is centralized logging implemented to support observability?
- What tools are used to visualize data and provide insights into workload performance?
Roles and Responsibilities
Monitoring Specialist
Responsibilities:
- Define KPIs for monitoring workload performance based on business requirements.
- Set up and maintain monitoring tools to ensure that metrics are collected effectively.
Logging Specialist
Responsibilities:
- Implement centralized logging for capturing and storing workload logs.
- Ensure logs are accessible and correlate them for troubleshooting and performance analysis.
Tracing Specialist
Responsibilities:
- Implement distributed tracing to track requests through the workload and identify bottlenecks.
- Use tracing data to recommend optimizations and improve workload performance.
Artifacts
- KPI Definition Document: A document outlining key performance indicators (KPIs) for the workload, including their business relevance and thresholds.
- Logging Configuration Document: A document detailing the centralized logging setup, including sources, storage, and access procedures.
- Tracing Implementation Guide: A guide for implementing distributed tracing, including tools used, components monitored, and data interpretation.
Relevant AWS Tools
Monitoring Tools
- Amazon CloudWatch: Provides metrics, dashboards, and alerts to help monitor workload health and performance based on defined KPIs.
Visualization Tools
- Amazon QuickSight: Visualizes data collected from monitoring and logging tools, allowing teams to create interactive dashboards for real-time insights.
- Amazon Managed Grafana: Integrates with CloudWatch and other AWS data sources to provide visualizations and alerts for your workload, helping teams understand system health at a glance.
Table of Contents