Cloud Configuration Invocation Rate Control

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Implementing wide-scale changes in a cloud computing environment can lead to instability due to the lack of sufficient safety controls, resulting in unintended negative effects on managed instances.

Innovation Solution

A configuration management system that uses an invocation rate parameter to control the rate at which configuration commands are applied to multiple instances, allowing for multi-stage invocation plans and customizable error thresholds to manage the impact and limit unintended effects.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If configuration commands are applied to all managed instances simultaneously, then the change implementation speed is improved, but the system stability deteriorates due to unintended negative effects and lack of safety controls

Engineering Contradiction:
Improvechange implementation speedVSAvoidsystem stability
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent segments the fleet of managed instances into multiple batches or groups, applying configuration commands to each batch sequentially rather than simultaneously. This allows the system to maintain high overall implementation speed while ensuring that if errors occur, they are contained within specific batches rather than affecting the entire fleet at once, thus preserving system stability.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements preliminary actions by performing validation checks, error threshold assessments, and staged rollouts before full-scale deployment. Configuration commands are first tested on a subset of instances, and only after verifying acceptable error rates and performance metrics are met does the system proceed to broader deployment, ensuring stability while maintaining productivity.

Inventive Principle:
Principle #10Preliminary action

2Productivity

If configuration commands are applied to a large number of instances, then the productivity is improved, but the error rate and unintended negative effects increase

Engineering Contradiction:
Improveconfiguration deployment scaleVSAvoiderror rate and unintended negative effects
Core Design Contradiction:
ProductivityVSObject-generated harmful factors

Solution Approach 1:

The patent implements feedback mechanisms that continuously monitor error rates, performance metrics, and system health during configuration deployment. When error thresholds are exceeded or unexpected behaviors are detected, the system automatically adjusts the deployment rate, pauses execution, or rolls back changes. This feedback loop enables large-scale deployment while maintaining low error rates by dynamically responding to system conditions.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The patent applies partial action by deploying configuration commands to a controlled subset of instances rather than the entire fleet simultaneously. By limiting the initial deployment scope and gradually expanding it based on observed performance, the system achieves high overall productivity while keeping the error rate and unintended negative effects manageable within each deployment wave.

Inventive Principle:
Principle #16Partial or excessive action

3Loss of time

If configuration commands are applied rapidly across multiple instances, then the time efficiency is improved, but the safety controls and error monitoring become insufficient

Engineering Contradiction:
Improveconfiguration deployment timeVSAvoidsafety controls and error monitoring
Core Design Contradiction:
Loss of timeVSReliability

Solution Approach 1:

The patent ensures continuity of useful action by implementing asynchronous monitoring and error checking that operates continuously alongside configuration deployment. Rather than pausing deployment for validation, the system performs safety checks and error monitoring in parallel, allowing rapid configuration propagation while maintaining robust safety controls and real-time error detection across all instances.

Inventive Principle:
Principle #20Continuity of useful action

Data Source

PatentUS10536332B1Configuration invocation management
Publication Date: 2020.01.14 AMAZON TECH INC
  • US10536332B1 patent drawing
  • US10536332B1 patent drawing
  • US10536332B1 patent drawing

AI summary

A system for managing configuration of multiple computing systems associated with a customer in a cloud computing environment. A command associated with the desired configuration is identified for execution on a total quantity of instances associated with the customer system to be configured. An invocation rate parameter selected by the customer system is used to control a rate in which the configuration command is invoked on the targeted instances. Based on the invocation rate parameter, the system invokes the configuration command on identified portions or sets of the targeted instances during different stages of the configuration invocation.