Specialized Cloud Regions for Availability-Sensitive Workloads

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Cloud provider networks face challenges in maintaining high availability for workloads sensitive to downtime due to correlated failures between regions, despite geographic isolation and redundant systems, as software updates can introduce defects simultaneously across regions.

Innovation Solution

Introducing specialized regions that receive software updates last and over a prolonged period to detect defects early, and temporarily halting updates if an outage occurs in another region or if a user fails over to the specialized region, ensuring additional resiliency and stability.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If software updates are deployed simultaneously across all regions, then deployment efficiency is improved, but correlated failures occur between regions

Engineering Contradiction:
Improvedeployment efficiencyVSAvoidavailability
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent segments the deployment process by introducing specialized regions that receive software updates at different times from standard regions. This temporal segmentation allows defect detection in standard regions before updates reach specialized regions, preventing correlated failures across all regions while maintaining deployment efficiency through controlled parallel updates.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent applies preliminary action by deploying software updates to standard regions first before deploying to specialized regions. This staged approach allows the system to detect and address defects early in the deployment process, preventing widespread failures while maintaining overall deployment efficiency through the predefined update sequence.

Inventive Principle:
Principle #10Preliminary action

2Measurement precision

If specialized regions receive updates last, then defect detection is improved, but deployment time increases

Engineering Contradiction:
Improvedefect detectionVSAvoiddeployment time
Core Design Contradiction:
Measurement precisionVSLoss of time

Solution Approach 1:

The patent segments the update deployment into two parallel tracks: standard regions receive updates first for defect detection, while specialized regions receive updates later. This segmentation enables defect detection without significantly increasing total deployment time, as updates proceed through coordinated stages rather than sequential bottlenecks.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent applies partial action by updating only standard regions first before updating specialized regions. This partial deployment strategy enables defect detection in a subset of regions, reducing the risk of widespread failures while minimizing the overall time impact compared to updating all regions simultaneously or sequentially.

Inventive Principle:
Principle #16Partial or excessive action

3Reliability

If geographic isolation is used between regions, then failure independence is improved, but correlated software failures occur

Engineering Contradiction:
Improvefailure independenceVSAvoidcorrelated software failures
Core Design Contradiction:
ReliabilityVSObject-affected harmful factors

Solution Approach 1:

The patent segments regions into standard and specialized categories with different update deployment schedules. This segmentation maintains geographic isolation benefits while addressing correlated software failures through temporal separation of updates, allowing defects to be detected and resolved before affecting all regions.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent applies preliminary action by deploying updates to standard regions before specialized regions. This preliminary deployment allows the system to detect software defects early and prevent them from propagating to specialized regions, thereby eliminating correlated software failures while maintaining geographic isolation.

Inventive Principle:
Principle #10Preliminary action

4Stability of the object's composition

If updates are deployed to all regions simultaneously, then service consistency is improved, but availability risk increases

Engineering Contradiction:
Improveservice consistencyVSAvoidavailability risk
Core Design Contradiction:
Stability of the object's compositionVSReliability

Solution Approach 1:

The patent applies preliminary action by deploying updates to standard regions first and monitoring for defects before deploying to specialized regions. This staged approach maintains service consistency through coordinated updates while reducing availability risk by preventing widespread failures through early defect detection in standard regions.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS11372634B1Specialized cloud provider regions for availability-sensitive workloads
Publication Date: 2022.06.28 AMAZON TECH INC
  • US11372634B1 patent drawing
  • US11372634B1 patent drawing
  • US11372634B1 patent drawing

AI summary

Techniques are described that enable a cloud provider network to provide specialized regions that can be used to achieve greater availability assurance for workloads highly sensitive to downtime or outages. Cloud provider network users may use specialized regions to complement the use of provider network services offered in other geographic regions defined by the cloud provider network, either to host redundant computing resources or for failover purposes, where the operation of a specialized region is designed to provide additional resiliency against various types of correlated failures among the geographic regions. As one example, a cloud provider network may stage deployments of software updates to the web services provided by the cloud provider network in a manner that ensures that specialized regions receive such updates last and over a relatively long period of time, thereby helping to ensure that any software defects are detected in an earlier deployment of the update.