Skip to main content

⭐ Repository → 💼 AWS Well-Architected

💼 Reliability

  • ID: /frameworks/aws-well-architected/reliability

Description​

Empty...

Similar​

Sub Sections​

SectionSub SectionsInternal RulesPoliciesFlagsCompliance
💼 Change management3no data
　💼 Design your workload to adapt to changes in demand4no data
　　💼 REL07-BP01 Use automation when obtaining or scaling resourcesno data
　　💼 REL07-BP02 Obtain resources upon detection of impairment to a workloadno data
　　💼 REL07-BP03 Obtain resources upon detection that more resources are needed for a workloadno data
　　💼 REL07-BP04 Load test your workloadno data
　💼 Implement change5no data
　　💼 REL08-BP01 Use runbooks for standard activities such as deploymentno data
　　💼 REL08-BP02 Integrate functional testing as part of your deploymentno data
　　💼 REL08-BP03 Integrate resiliency testing as part of your deploymentno data
　　💼 REL08-BP04 Deploy using immutable infrastructureno data
　　💼 REL08-BP05 Deploy changes with automationno data
　💼 Monitor workload resources7no data
　　💼 REL06-BP01 Monitor all components for the workload (Generation)no data
　　💼 REL06-BP02 Define and calculate metrics (Aggregation)no data
　　💼 REL06-BP03 Send notifications (Real-time processing and alarming)no data
　　💼 REL06-BP04 Automate responses (Real-time processing and alarming)no data
　　💼 REL06-BP05 Analyze logsno data
　　💼 REL06-BP06 Regularly review monitoring scope and metricsno data
　　💼 REL06-BP07 Monitor end-to-end tracing of requests through your systemno data
💼 Failure management5no data
　💼 Back up data4no data
　　💼 REL09-BP01 Identify and back up all data that needs to be backed up, or reproduce the data from sourcesno data
　　💼 REL09-BP02 Secure and encrypt backupsno data
　　💼 REL09-BP03 Perform data backup automaticallyno data
　　💼 REL09-BP04 Perform periodic recovery of the data to verify backup integrity and processesno data
　💼 Design your workload to withstand component failures7no data
　　💼 REL11-BP01 Monitor all components of the workload to detect failuresno data
　　💼 REL11-BP02 Fail over to healthy resourcesno data
　　💼 REL11-BP03 Automate healing on all layersno data
　　💼 REL11-BP04 Rely on the data plane and not the control plane during recoveryno data
　　💼 REL11-BP05 Use static stability to prevent bimodal behaviorno data
　　💼 REL11-BP06 Send notifications when events impact availabilityno data
　　💼 REL11-BP07 Architect your product to meet availability targets and uptime service level agreements (SLAs)no data
　💼 Plan for Disaster Recovery (DR)5no data
　　💼 REL13-BP01 Define recovery objectives for downtime and data lossno data
　　💼 REL13-BP02 Use defined recovery strategies to meet the recovery objectivesno data
　　💼 REL13-BP03 Test disaster recovery implementation to validate the implementationno data
　　💼 REL13-BP04 Manage configuration drift at the DR site or Regionno data
　　💼 REL13-BP05 Automate recoveryno data
　💼 Test reliability5no data
　　💼 REL12-BP01 Use playbooks to investigate failuresno data
　　💼 REL12-BP02 Perform post-incident analysisno data
　　💼 REL12-BP03 Test scalability and performance requirementsno data
　　💼 REL12-BP04 Test resiliency using chaos engineeringno data
　　💼 REL12-BP05 Conduct game days regularlyno data
　💼 Use fault isolation to protect your workload3no data
　　💼 REL10-BP01 Deploy the workload to multiple locationsno data
　　💼 REL10-BP02 Automate recovery for components constrained to a single locationno data
　　💼 REL10-BP03 Use bulkhead architectures to limit scope of impactno data
💼 Foundations2no data
　💼 Manage service quotas and constraints6no data
　　💼 REL01-BP01 Aware of service quotas and constraintsno data
　　💼 REL01-BP02 Manage service quotas across accounts and regionsno data
　　💼 REL01-BP03 Accommodate fixed service quotas and constraints through architectureno data
　　💼 REL01-BP04 Monitor and manage quotasno data
　　💼 REL01-BP05 Automate quota managementno data
　　💼 REL01-BP06 Ensure that a sufficient gap exists between the current quotas and the maximum usage to accommodate failoverno data
　💼 Plan your network topology5no data
　　💼 REL02-BP01 Use highly available network connectivity for your workload public endpointsno data
　　💼 REL02-BP02 Provision redundant connectivity between private networks in the cloud and on-premises environmentsno data
　　💼 REL02-BP03 Ensure IP subnet allocation accounts for expansion and availabilityno data
　　💼 REL02-BP04 Prefer hub-and-spoke topologies over many-to-many meshno data
　　💼 REL02-BP05 Enforce non-overlapping private IP address ranges in all private address spaces where they are connectedno data
💼 Workload architecture3no data
　💼 Design interactions in a distributed system to mitigate or withstand failures7no data
　　💼 REL05-BP01 Implement graceful degradation to transform applicable hard dependencies into soft dependenciesno data
　　💼 REL05-BP02 Throttle requestsno data
　　💼 REL05-BP03 Control and limit retry callsno data
　　💼 REL05-BP04 Fail fast and limit queuesno data
　　💼 REL05-BP05 Set client timeoutsno data
　　💼 REL05-BP06 Make systems stateless where possibleno data
　　💼 REL05-BP07 Implement emergency leversno data
　💼 Design interactions in a distributed system to prevent failures4no data
　　💼 REL04-BP01 Identify the kind of distributed systems you depend onno data
　　💼 REL04-BP02 Implement loosely coupled dependenciesno data
　　💼 REL04-BP03 Do constant workno data
　　💼 REL04-BP04 Make mutating operations idempotentno data
　💼 Design your workload service architecture3no data
　　💼 REL03-BP01 Choose how to segment your workloadno data
　　💼 REL03-BP02 Build services focused on specific business domains and functionalityno data
　　💼 REL03-BP03 Provide service contracts per APIno data