Amazon Technologies, Inc.

Eric Samuel Stone

Derek Solomon Pai

Shawn Jones

Ahmed Usman Khalid

Mihir Rajendrabhai Patel

Jon R Jay

Yung-Chun Lin

Jeremy A Dashe

Kenneth C Macfarlane

Thomas Hans Deml

Alexander Kulikov

Anthony Nicholas Liguori

Nikita Pinski

Nathan Brent Glissmeyer

Kunal Chopra

Raymond P Sharpe, Jr

Steven Anthony Kady

Benjamin Jeffery

Mingzhe Zhu

Yang Lin

Richard Hazen Galliher, Iii

Kai Fan Tang

Mai-Lan Tomsen Bukovec

David James Goodell

William Ashley

Alison Qing-Ning Truong

Patrick John Lawrence

Avigdor Segal

Clint Joseph Sbisa

Matthew B Barr

Jonathan Chocron

Jonathan Welter Mullen

Steven Douglas Robinson

Vitaly Ostrovsky

Tal Avraham

Tatiana Cooke

Abhishek Katuluru

Paul Sharpe

Nate Glissmeyer

Raymond P Sharpe

A networking manager of an extension server of a virtualized computing service detects that a data link layer frame has been obtained at the extension server. The networking manager delivers at least a portion of contents of the frame to a compute instance running at the extension server in response to determining that a destination media access control (MAC) address of the frame matches a MAC address of a local-premise-access virtual network interface attached to the compute instance. The local-premise-access virtual network interface is not assigned an Internet Protocol (IP) address from a range of IP addresses managed by the virtualized computing service.

Virtual network interfaces for managed layer-2 connectivity at computing service extension locations

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.

Standby instances for auto-scaling groups

A first service of a provider network obtains an identification of one or more substrate addressable devices included in an extension of the provider network. Based on the identification, a launch of one or more compute instances within the provider network is initiated. The one or more compute instances are to connect the provider network to the extension of the provider network across at least a third-party network by receiving a first control plane message directed to a first substrate addressable device of the one or more substrate addressable devices, by updating a message state data store based at least in part on the first control plane message, and by sending a second control plane message to the first substrate addressable device via a secure tunnel.

Provider network connectivity management for provider network substrate extensions

A first message of a first type and having a first destination address is received in a provider network. The first destination address is associated with a virtual network address of the provider network and an address of a first device in an extension of the provider network, the extension of the provider network in communication with the provider network via at least a third-party network. A message state data store is updated based on at least a portion of the first message. A first payload of the first message is sent to the first device a first secure tunnel through the third-party network.

Provider network connectivity to provider network substrate extensions

A transaction directed to a hierarchy of data objects stored in a non-transactional data store may be executed. The transaction may be received and description of the transaction stored in a parent data object of the hierarchy. Upon storing the description of the transaction, the transaction may be acknowledged as committed. Access requests for the hierarchy of data objects may be serviced by accessing the description of the transaction and applying to child data objects in the hierarchy returned for servicing a query directed to the hierarchy. A new transaction that is received may initiate application of the transaction according to the description in the parent data object with respect to child data objects.

Executing transactions for a hierarchy of data objects stored in a non-transactional data store

A secondary index may be implemented for a distributed data set that is strongly consistent. Updates to a distributed data set that add or remove items from the distributed data set may be reflected in the secondary index as part of performing the update. Pointers to items to be added to a distributed data set may be included in the secondary index as part of processing an insertion request for the new items. Pointers to items removed from a distributed data set may be removed from the secondary index as part of processing a deletion request. Changes to the secondary index may be performed so that the secondary index does not fail to identify items that are present in the distributed data set.

Strongly-consistent secondary index for a distributed data set

A computing resource associated with a user is scheduled to undergo a transition. Prior to the scheduled transition, the computing resource is placed in a pending state. The user is notified that the computing resource is scheduled to undergo the transition. In response to an input received from the user, the computing resource is allowed to undergo the transition when the input indicates that the transition can proceed.

Computing resource transition notification and pending state

A method and apparatus for provisioning a computing resource is provided. Provisioning a computing resource based on a provisioning policy is initiated. The provisioning policy may specify one or more supplementary operations whose successful completion is optional for the computing resource to be used. Further in the method and apparatus, the computing resource is provided for use.

Computer resource provisioning failure mitigation

Migration of mutable data sets between data stores may be implemented. Multiple data sets may be stored at a source data store. Some of the data sets may be identified for migration to a destination data store. Updates to the identified data sets may be blocked while the identified data sets are copied from the source data store to the destination data store. In some embodiments, the copies of the data sets at the destination data store are validated. Updates to the data sets may then be allowed at the destination data store instead of the source data store.

Migration of mutable data sets between data stores

A computing resource service provider may provide computing instances organized in to logical groups, such as auto-scaling groups. Computing instances assigned to an auto-scaling group may be detached from auto-scaling group. Detached instances may no longer be managed by the auto-scaling group and may not contribute to the capacity of the auto-scaling group for auto-scaling purposes.

Detaching instances from auto-scaling group

Technology for scaling computing instances is provided. In one example, a method may include identifying vertical scaling rules defining a criterion for vertically scaling a computing instance from a first instance type to a second instance type. The method may further include monitoring usage of the computing instance and vertically scaling the computing instance from the first instance type to the second instance type based on the usage as compared to the vertical scaling rules.

Vertical scaling of computing instances

Aspects of systems and methods for maintaining and operating agent nodes are provided. In some embodiments, calls, contacts, and other work units may be routed to individual customer service agents via a centralized queue based on a variety of factors. Some embodiments may provide market-based call pricing and customer service agent compensation.

System and method for automated call distribution

Approaches are described for enabling a user to specify one or more termination policies that can be used to select which instances in a group of virtual machines (or other compute resources) allocated to the user should be terminated first when scaling down the group of virtual machine instances. The termination policies can be utilized by an automatic scaling service when managing the resources in a multitenant shared resource computing environment, such as a cloud computing environment.

Termination policies for scaling compute resources

Techniques are described for scaling a group of computing resources. A computing resource service receives a scaling policy for use in scaling the group of computing resources. The scaling policy specifies a target level for a resource utilization metric and magnitude-based changes to the group. The computing resource service receives information about a magnitude of a measurement for the resource utilization metric. The computing resource service determines, based at least in part on the scaling policy, one or more changes for the group and initiates the one or more changes in the group.

Growing community of inventors

Seattle, WA, United States of America

Eric Samuel Stone