-
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
Use build and deployment management systems
Using Build and Deployment Management Systems for Reliability
Build and deployment management systems are crucial for automating the process of building, testing, and deploying software. By using these systems, organizations can reduce errors associated with manual deployments, improve the efficiency of deployment pipelines, and ensure consistency across environments. Automation in build and deployment processes results in greater reliability, faster deployments, and fewer production issues.
Automate Builds and Deployments
Use build and deployment management systems to automate the entire process from code commit to production deployment. Automation helps eliminate the manual errors that often occur during the build and deployment stages, ensuring that applications are consistently built and deployed according to defined standards. Automated processes lead to more reliable deployments and faster releases.
Track Build and Deployment Status
Track the status of builds and deployments in real-time to gain visibility into the release pipeline. Build and deployment management systems provide insights into the status of ongoing builds, successful deployments, and failed releases. This visibility enables teams to react quickly if issues arise and understand where the problem occurred in the pipeline.
Standardize Build and Deployment Pipelines
Use standardized templates and scripts to ensure that build and deployment processes are repeatable and consistent. Standardizing the steps involved in building and deploying applications helps reduce variability and ensures that best practices are consistently followed. This standardization also facilitates scaling by making it easy to replicate pipelines for new projects or environments.
Integrate Testing into the Pipeline
Integrate automated testing within the build and deployment management systems to validate changes before they are deployed. Including tests, such as unit tests, integration tests, and performance tests, ensures that only validated and error-free code is promoted to production. This integration helps catch defects early and reduce the number of issues in production.
Reduce Manual Errors and Deployment Effort
Automating the build and deployment processes significantly reduces the level of effort required to release changes, freeing up team members to focus on higher-value activities. By eliminating manual steps, teams can also minimize the risk of human error, resulting in smoother and more predictable deployments.
Supporting Questions
- How are build and deployment management systems used to automate the release pipeline?
- How do build and deployment management systems help reduce errors and effort in the deployment process?
- How is automated testing integrated into the build and deployment pipeline?
Roles and Responsibilities
Build Engineer
Responsibilities:
- Set up and maintain build management systems to automate the process of building software.
- Ensure that build automation scripts are up-to-date and follow best practices.
Deployment Engineer
Responsibilities:
- Manage deployment processes, ensuring that deployment management systems are effectively used to automate releases.
- Track deployment status and resolve issues if they occur during the deployment process.
QA Engineer
Responsibilities:
- Integrate testing scripts into the build and deployment pipeline to validate changes before deployment.
- Ensure that testing is comprehensive and automated to reduce the likelihood of defects reaching production.
Artifacts
- Build and Deployment Pipeline Diagram: A diagram illustrating the steps involved in building and deploying software, including points of automation.
- Deployment Checklist: A checklist used to ensure all required steps are completed and validated before software is deployed to production.
- Deployment Logs: Logs capturing details of each deployment, including status, changes, and any errors encountered.
Relevant AWS Tools
Build and Deployment Management Tools
- AWS CodeBuild: Automates the process of compiling source code, running tests, and producing build artifacts, reducing the manual effort required to build software.
- AWS CodeDeploy: Automates the deployment of applications to Amazon EC2 instances, AWS Fargate, and other compute services, ensuring consistent and reliable deployments.
Pipeline Automation Tools
- AWS CodePipeline: Orchestrates the entire release process, integrating with build, test, and deployment tools to automate the end-to-end software delivery pipeline.
- AWS CodeStar: Provides a unified interface to manage the development lifecycle, including automated build and deployment processes.
Monitoring and Logging Tools
- Amazon CloudWatch: Monitors build and deployment pipelines, providing metrics and alerts to track the success of releases and identify any issues.
- AWS CloudTrail: Logs all API activities related to builds and deployments, helping teams audit changes and troubleshoot any problems that arise during the deployment process.