Flexible Maintenance Windows for Cloud Instance Scheduling

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current maintenance practices in service provider networks often disrupt customer workloads due to inflexible maintenance scheduling, leading to downtime, latency, and operational overhead, as customers have limited control over when maintenance events occur.

Innovation Solution

Customers can specify flexible maintenance event windows and customize notifications through graphical user interfaces, command line interfaces, or APIs, allowing the service provider to schedule maintenance during less disruptive times, optimizing fleet maintenance and minimizing disruptions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If maintenance is scheduled according to a fixed maintenance schedule, then the service provider can ensure fleet health and security, but customers experience disruptions to their workloads including downtime and latency

Engineering Contradiction:
Improvefleet healthVSAvoidworkload availability
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The maintenance schedule is transformed from a fixed, static timetable to a dynamic, flexible arrangement that adapts to customer workload patterns. The system allows maintenance windows to be adjusted based on real-time workload conditions, enabling the service provider to maintain fleet health while minimizing disruptions to customer productivity.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system performs preliminary actions by notifying customers in advance of scheduled maintenance events and allowing them to proactively complete maintenance activities before the defined maintenance schedule. This advance notice and opportunity for early action reduces unexpected disruptions while maintaining security and health standards.

Inventive Principle:
Principle #10Preliminary action

2Productivity

If customers proactively manage maintenance events, then maintenance can be completed at optimal times, but operational overhead increases for customers

Engineering Contradiction:
Improvemaintenance timing optimizationVSAvoidoperational overhead
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The system enables self-service by allowing customers to autonomously manage their maintenance events through automated notifications and flexible scheduling capabilities. Customers can independently adjust maintenance windows and coordinate with service providers without requiring extensive operational intervention, reducing overhead while maintaining optimization benefits.

Inventive Principle:
Principle #25Self-service

3Device complexity

If maintenance events are scheduled inflexibly, then service provider operations are simplified, but customer workload disruptions increase

Engineering Contradiction:
Improvescheduling complexityVSAvoidworkload continuity
Core Design Contradiction:
Device complexityVSProductivity

Solution Approach 1:

The maintenance scheduling system transitions from a rigid, inflexible structure to a dynamic framework that can adapt to varying customer needs and workload patterns. This dynamic approach maintains relatively simple service provider operations while significantly improving workload continuity by allowing flexible adjustment of maintenance timing.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS11354150B1Utilizing maintenance event windows to determine placement of instances
Publication Date: 2022.06.07 AMAZON TECH INC
  • US11354150B1 patent drawing
  • US11354150B1 patent drawing
  • US11354150B1 patent drawing

AI summary

This disclosure describes techniques for flexible maintenance windows for performing maintenance for instances. Using techniques described herein, a user of a service provider network may specify configuration data that relates to maintenance events of instances. A “maintenance event” is any event that relates to deploying instances and/or at least temporarily losing use of an instance. For example, a maintenance event may cause an instance to be deployed, re-booted, re-started, or replaced. According to some configurations, customers may specify one or more maintenance event windows for when maintenance is to be performed, as well as customize notifications that are provided to the customer about scheduled maintenance events. For instance, customers may create a maintenance window that specifies to perform maintenance on Tuesdays, between 2 AM-3 AM, and that notifications are to include information specified by the customer (e.g., through one or more tags).