Standby instances for auto-scaling groups

Patent metadata

Field	Value
Publication number	US-9647889-B1
Application number	US-201414539871-A
Country	US
Kind code	B1
Filing date	Nov 12, 2014
Priority date	Nov 12, 2014
Publication date	May 9, 2017
Grant date	May 9, 2017

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:
receiving an application programming interface call to place a computer system instance of an auto-scaling group into standby, wherein a first set of computer system instances is assigned to the auto-scaling group;
determining that fulfillment of the received application programming interface call complies with a setting of the auto-scaling group and that the computer system instance can be placed into standby;
updating a capacity of the auto-scaling group;
initiating a workflow to place the computer system instance into standby by at least:
deregistering the computer system instance from a load balancer associated with the auto-scaling group, thereby preventing the load balancer from sending request processing traffic to the computer system instance; and
removing the computer system instance from a second set of computer system instances for which utilization information specific to the auto-scaling group is obtained; and

fulfilling the application programming interface call as a result of having placed the computer system instance in standby so that the computer system instance continues to run but does not contribute to the capacity of the auto-scaling group.

2. The computer-implemented method of claim 1 , wherein the computer-implemented method further includes:
receiving a request for information about the first set of computer system instances assigned to the auto-scaling group; and
providing the requested information about the first set of computer system instances including information about the computer system instance in standby.

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

4. The computer-implemented method of claim 1 , wherein the computer-implemented method further includes:
receiving a second application programming interface call to place the standby computer system instance of the auto-scaling group into service for the auto-scaling group;
determining that fulfillment of the received second application programming interface call complies with a setting of the auto-scaling group and the standby computer system instance can be placed into service for the auto-scaling group;
updating the capacity of the auto-scaling group; and
initiating a second workflow to place the standby computer system instance into service by at least:
registering the standby computer system instance with the load balancer associated with the auto-scaling group; and
adding the standby computer system instance to the second set of computer system instances for which utilization information specific to the auto-scaling group is obtained.

5. A system, comprising:
one or more processors; and
memory with instructions that, when executed by the one or more processors, cause the system to:
receive an application programming interface call to place an instance of an auto-scaling group into standby, wherein a set of instances is assigned to the auto-scaling group; and
respond to the application programming interface call by:
removing the instance from a load balancer configured to manage traffic for the auto-scaling group, thereby preventing the load balancer from sending request processing traffic to the computer system instance;
removing the instance from a metrics service configured to obtain utilization information for the auto-scaling group; and
updating a capacity of the auto-scaling group, wherein the instance continues to run after being placed into standby.

6. The system of claim 5 , wherein the memory further includes instructions that, when executed by the one or more processors, cause the system to determine the auto-scaling group to which the instance is assigned based at least in part on the application programming interface call.

7. The system of claim 5 , wherein the instructions that cause the system to update the capacity of the auto-scaling group 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 the application programming interface call.

8. The system of claim 5 , wherein the memory further includes instructions that, when executed by the one or more processors, cause the system to transmit a status update for the instances assigned to the auto-scaling group, wherein the status update includes information about the instance placed into standby.

9. The system of claim 5 , wherein the memory further includes instructions that, when executed by the one or more processors, cause the system to execute a health check on one or more of the instances assigned to the auto-scaling group including the instance placed into standby.

10. The system of claim 5 , wherein the memory further includes instructions that, when executed by the one or more processors, cause the system to, in response to a second application programming interface call to move the instance into service in the auto-scaling group, move the instance placed into standby into service in the auto-scaling group.

11. The system of claim 5 , wherein application programming interface call 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 5 , wherein the memory further includes instructions that, when executed by the one or more processors, cause the system to provide, in response to receiving the application programming interface call, job information associated with the application programming call, the job information configured to enable status checks on a workflow initiated to fulfill the application programming interface call.

13. A non-transitory computer-readable storage medium having stored thereon executable instructions that, when executed by one or more processors of a computer system, cause the computer system to at least:
receive a request to move an instance of an auto-scaling group from in service to standby;
move the instance to standby such that the instance is still within the auto-scaling group but does not contribute to a capacity of the auto-scaling group, thereby preventing a load balancer from sending request processing traffic to the computer system instance; and
update the capacity of the auto-scaling group based at least in part on the instance being moved into standby.

14. The non-transitory computer-readable storage medium of claim 13 , wherein the instructions that cause the computer system to move the instance to standby further cause the computer system to remove the instance from a set of instances for which utilization information specific to the auto-scaling group is obtained.

15. The non-transitory computer-readable storage medium of claim 13 , wherein the instructions that cause the computer system to move the instance to standby further cause the computer system to deregister the instance from a load balancer associated with the auto-scaling group.

16. The non-transitory computer-readable storage medium of claim 13 , wherein the instructions further comprise instructions that, when executed by the one or more processors, cause the computer system to determine that the instance is a member of the auto-scaling group.

17. The non-transitory computer-readable storage medium of claim 13 , wherein

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

• H04L41/082

  the condition being updates or upgrades of network functionality · 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

• H04L67/1031

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