Standby instances for auto-scaling groups

Patent metadata

Field	Value
Publication number	US-11296941-B2
Application number	US-201816005328-A
Country	US
Kind code	B2
Filing date	Jun 11, 2018
Priority date	Nov 12, 2014
Publication date	Apr 5, 2022
Grant date	Apr 5, 2022

Abstract

A computing resource service provider may provide computing instances organized into logical groups, such as auto-scaling groups. Computing instances assigned to an auto-scaling group may be place into standby. Standby instances may still be managed by the auto-scaling group but may not contribute to the capacity of the auto-scaling group for auto-scaling purposes.

First claim

What is claimed is:

1. A computer-implemented method, comprising:
obtaining a set of metrics associated with a first set of computer system instances of an auto-scaling group and used to trigger scaling operations of the auto-scaling group, the set of metrics including a first measure of request processing traffic directed to the auto-scaling group and a second measure of a capacity of the auto-scaling group to process the request processing traffic;
deregistering a first computer system instance from a load balancer associated with the auto-scaling group to prevent the load balancer from sending at least a portion of the request processing traffic to the first computer system instance, the first computer system instance being a member of the first set of computer system instances;
placing the first computer system instance in standby so that the first computer system instance continues to run but does not contribute to the second measure; and
modifying the set of metrics by at least decrementing the second measure by at least a first capacity value associated with the first computer system instance in standby.

2. The computer-implemented method of claim 1 , wherein deregistering the first computer system instance from the load balancer associated with the auto-scaling group is based at least in part on a request from a user account associated with the first set of computer system instances of the auto-scaling group.

3. The computer-implemented method of claim 1 , wherein the computer implemented method further includes removing the first computer system instance from the first set of computer system instances based at least in part on deregistering the first computer system instance from the load balancer associated with the auto-scaling group.

4. The computer-implemented method of claim 1 , wherein the computer implemented method further includes sending to a customer device, in response to a request for information about a second set of computer system instances assigned to the auto-scaling group, the information indicating at least:
the second set of computer system instances; and
the first computer system instance in standby to the customer device.

5. The computer-implemented method of claim 1 , wherein the computer implemented method further includes:
obtaining a request to place the first computer system instance of the auto-scaling group into service for the auto-scaling group and to remove the first computer system instance from standby; and
updating the second measure of the auto-scaling group based at least in part on determining that fulfillment of the request complies with a setting of the auto-scaling group and the first computer system instance can be placed into service for the auto-scaling group.

6. The computer-implemented method of claim 5 , wherein the computer implemented method further includes:
initiating a workflow to place the first computer system instance into service by at least:
registering the first computer system instance with the load balancer associated with the auto-scaling group; and
adding the first computer system instance to the first set of computer system instances for which the set of metrics is obtained.

7. The computer-implemented method of claim 1 , wherein the computer implemented method further includes fulfilling a request to interact with the first computer system instance in standby, the request fulfilled by an instance service separate from the auto-scaling group.

8. The computer-implemented method of claim 1 , further comprising:
obtaining a request to place the first computer system instance of the auto-scaling group into standby, wherein a second set of computer system instances are assigned to the auto-scaling group; and
updating the second measure based at least in part on determining that fulfillment of the request complies with a setting of the auto-scaling group and that the first computer system instance can be placed into standby.

9. A system, comprising:
one or more processors; and
memory having stored therein instructions that, as a result of being executed by the system, cause the system to:
obtain utilization information associated with an auto-scaling group and used to trigger scaling operations, the utilization information including at least a first value representing a portion of request processing traffic directed to the auto-scaling group;
remove an instance of the auto-scaling group from a load balancer to prevent the load balancer from sending the request processing traffic to the instance, the load balancer configured to manage traffic for the auto-scaling group; and
update a capacity of the auto-scaling group, wherein the instance continues to run after being placed into standby by at least reducing a second value associated with the capacity of the auto-scaling group by at least a capacity value associated with the instance placed into standby, where the second value corresponds to projected availability of the auto-scaling group to process the request processing traffic.

10. The system of claim 9 , wherein the instructions further cause the system to prevent a portion of the utilization information obtained from the instance from being accounted for by a metrics service, the metrics service obtaining the utilization information for the auto-scaling group after removing the instance of the auto-scaling group from the load balancer.

11. The system of claim 9 , wherein removing the instance from the load balancer configured to manage traffic for the auto-scaling group is in response to a request that includes information for identifying the instance, information for identifying the auto-scaling group, and information indicating to the auto-scaling group to decrement the capacity of the auto-scaling group.

12. The system of claim 9 , wherein the instructions further cause the system to, in response to a request to move the instance into service in the auto-scaling group, move the instance placed into standby into service in the auto-scaling group.

13. The system of claim 9 , wherein the instructions further cause the system to transmit, in response to a status update request, a status update for one or more instances assigned to the auto-scaling group, wherein the status update includes information about the instance placed into standby.

14. The system of claim 9 , wherein the instructions further cause the system to instantiate a replacement instance for the instance to be placed into standby based at least in part on information included in a request to place the instance into standby.

15. A set of non-transitory computer-readable storage media that stores executable instructions that, as a result of being executed by one or more processors of a computer system, cause the computer system to:
obtain a set of metrics for an auto-scaling group including at least a first metric representing a capacity of an auto-scaling group;
move an instance of the auto-scaling group to standby such that the instance is still within the auto-scaling group but does not contribute to the first metric of the auto-scaling group; and
update the capacity of the auto-scaling group based at least in part on the instance being moved into standby by at least reducing the first metric of the set of metrics representing the capacity of the auto-scaling group by at least a capacity value associated with the instance in standby.

16. The set of non-transitory computer-readable storage media of claim 15 , wherein the instructions that cause the computer system to move the instance to standby further cause the computer system to remove the

Assignees

• Amazon Tech Inc

Inventors

• Jones Shawn
• Stone Eric Samuel
• Pai Derek Solomon

Classifications

• G06F9/5077 Primary

  Logical partitioning of resources; Management or configuration of virtualized resources (specific details on emulation or internal functioning of virtual machines G06F9/455) · CPC title

• G06F9/547

  Remote procedure calls [RPC]; Web services · CPC title

• H04L41/0823 Primary

  characterised by the purposes of a change of settings, e.g. optimising configuration for enhancing reliability (for optimising operational conditions of wireless networks H04W24/02) · CPC title

• H04L41/0816

  the condition being an adaptation, e.g. in response to network events · CPC title

• H04L67/1031

  Controlling of the operation of servers by a load balancer, e.g. adding or removing servers that serve requests · CPC title