Abstract:
A computing resource service provider may provide computing instances organized into logical groups, such as auto-scale groups. Computing instances assigned to an auto-scale group may be associated with one or more load balancers configured to direct traffic to the computing instances. Furthermore, customers of the computing resource service provider may add or remove load balancer from the auto-scale groups. A background process may be used to add and remove computer instances of the auto-scale group from the load balancers customers are attempting to have added or removed.
Abstract:
In response to receipt of a notification from a third service, a scaling policy specified by a customer of a computing resource service provider to be associated with the notification is obtained, with the scaling policy including a set of parameters that includes an identity of a resource of a second service of the computing resource service provider. As a result of processing the scaling policy in accordance with the set of parameters, a request is submitted to a second service to scale the resource, and output is provided that indicates whether the scaling request has been fulfilled.
Abstract:
A notification for an application stack is received, where the application stack includes a plurality of resource types. At least one policy associated with the notification is obtained, with the first policy being a policy for scaling a first resource of a first resource type and a second resource of a second resource type of the application stack. A first capacity for the first resource and a second capacity for the second resource is determined based at least in part on the at least one policy. The first resource and the second resource are caused to be scaled according to the first capacity and the second capacity respectively.
Abstract:
A computing resource service provider may provide computing instances organized into logical groups, such as auto-scale groups. Computing instances assigned to an auto-scale group may be associated with one or more load balancers configured to direct traffic to the computing instances. Furthermore, customers of the computing resource service provider may add or remove load balancer from the auto-scale groups. A background process may be used to add and remove computer instances of the auto-scale group form the load balancers customers are attempting to have added or removed.
Abstract:
A computing resource service provider may provide computing instances organized into logical groups, such as auto-scale groups. Computing instances assigned to an auto-scale group may be associated with one or more load balancers configured to direct traffic to the computing instances. Furthermore, customers of the computing resource service provider may add or remove load balancer from the auto-scale groups.
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 associated with one or more load balancers configured to direct traffic to the computing instances. Furthermore, customers of the computing resource service provider may add or remove load balancer from the auto-scaling groups. The computing resource service provider may track a state of the load balancer in a database in order to enable efficient addition and removal of load balancers to auto-scale groups.
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 associated with one or more load balancers configured to direct traffic to the computing instances. Furthermore, customers of the computing resource service provider may add or remove load balancer from the auto-scaling groups. The computing resource service provider may track a state of the load balancer in a database in order to enable efficient addition and removal of load balancers to auto-scale groups.
Abstract:
Techniques for a service provider network to communicatively couple services and/or applications in a serverless computing environment. A pipe component can configure a pipe to integrate two services by transmitting data between services and/or applications using the pipe. The pipe may also be configured to transform how a service processes an event, control timing of event transmissions using the pipe, define an event structure for an event, and/or batch events. Pipes enable an application or service to exchange data with a variety of services provided by the service provider network while controlling what type of data is generated, stored, or transmitted.
Abstract:
Techniques for a service provider network to communicatively couple services and/or applications in a serverless computing environment. A pipe component can configure a pipe to integrate two services by transmitting data between services and/or applications using the pipe. The pipe may also be configured to transform how a service processes an event, control timing of event transmissions using the pipe, define an event structure for an event, and/or batch events. Pipes enable an application or service to exchange data with a variety of services provided by the service provider network while controlling what type of data is generated, stored, or transmitted.
Abstract:
A notification for an application stack is received, where the application stack includes a plurality of resource types. At least one policy associated with the notification is obtained, with the first policy being a policy for scaling a first resource of a first resource type and a second resource of a second resource type of the application stack. A first capacity for the first resource and a second capacity for the second resource is determined based at least in part on the at least one policy. The first resource and the second resource are caused to be scaled according to the first capacity and the second capacity respectively.