Amazon Technologies, Inc.

Colm MacCarthaigh

David R Richardson

Benjamin W S Redman

John David Cormie

Imran S Patel

Prashanth A Acharya

Bradley E Marshall

Craig Wesley Howard

Harvo Reyzell Jones

Jonathan B Corley

Ryan F Watson

Nathan Dye

Lee B Rosen

Ronald James Snyder, Jr

John K Loendorf

Benjamin Ws Redman

David Dzung Lu

Michael F Diggins

Xingbo Wang

Bryan Mark Benson

Diwakar Gupta

Ishwardutt Parulkar

Upendra Bhalchandra Shevade

Grant Alexander Macdonald McAlister

Dougal Stuart Ballantyne

Laurion Darrell Burchall

Narjala Prakash Bhasker

Devlin Roarke Dunsmore

Valeri Liborski

Nicholas Ryman Vogel

Jorgen Lawrence Johnson

Mikhail Ivanovich Golovnykh

Bashuman Deb

Anoop Dawani

Anshul Saxena

Grant Alexander McAlister

Benjamin WS Redman

A network address assigned to a virtual network interface of a packet transformation node of a flow management service is identified. A packet of a particular network flow associated with an application implemented at an isolated virtual network is sent to the network address. Using a rewrite directive generated at a rewriting decisions node of the service and cached at the packet transformation node, a transformed packet corresponding to a packet received at the packet transformation node is generated and transmitted to a destination.

Network flow management for isolated virtual networks

The present disclosure generally relates to managing a failover service. The failover service can receive a list of regions and a list of rules that must be satisfied for a region to be considered available for failover. The failover service can then determine the regions that satisfy each rule of the list of rules and are available for failover. The failover service can then deliver this information to a client. The failover service can determine the regions that do not satisfy one or more of the rules from the list of rules and deliver this information to a client. The failover service can perform automatic remediation to the unavailable failover regions and client remediation to the unavailable failover regions.

Managing failover region availability for implementing a failover service

Techniques for API-based endpoint discovery and centralized load balancing involving provider substrate extension resources are described. A discovery coordinator service located within a provider network can identify one or more endpoints from a set of potentially distributed endpoints for a client to utilize, where endpoints may be located within provider substrate extensions of the provider network. The discovery coordinator service can analyze the loads of these endpoints, via client lease information, to identify nearby, low-load resources that may be most optimal for the client to use via providing minimal latency of access.

Centralized load balancing of resources in cloud edge locations embedded in telecommunications networks

Techniques are described for managing preloading of data for client computing systems. A client computing system may provide one or more persistent data storage caches on local storage, such as to support a particular software program executing on the client computing system (e.g., a Web browser program, with the persistent data storage cache designed to store browser cookies and other data for later access by the Web browser program). Additional data may be stored in such a persistent data storage cache by preloading those data groups before they are requested by the client computing system (e.g., based on interactions of a user of the client computing system with an executing program on the client computing system). Particular data groups to preload may be selected in various manners, including to provide a specified type of minimum functionality to a client computing system based on the preloaded data groups.

Managing preloading of data on client systems

A system and method for the management of client computing device DNS queries and subsequent resource requests within a content delivery network service provider domain are provided. The management of the DNS queries can include the selection of computing devices corresponding to various Point of Presence locations for processing DNS queries. Additionally, the management of the content requests can include the selection of computing devices corresponding to resource cache components corresponding to various Point of Presence locations for providing requested content. The selection of the computing devices can incorporate logic related to geographic criteria, testing criteria, and the like.

Point of presence management in request routing

The present disclosure generally relates to managing a failover service for regions in an active-active configuration. The failover service can receive a list of regions and a list of rules that must be satisfied for a region to be considered available for failover. For each primary region of a plurality of primary regions, the failover service can then determine the regions that satisfy each rule of the list of rules and are available for failover. The failover service can then deliver this information to a client. The failover service can determine the regions that do not satisfy one or more of the rules from the list of rules and deliver this information to a client. The failover service can perform automatic remediation and client remediation to the unavailable failover regions.

The present disclosure generally relates to managing a failover service. The regional management service can receive a list of primary regions and a list of rules for each primary region that must be satisfied for a primary region to be considered available for failover from the respective primary region. The regional management service can then determine the primary regions that satisfy each rule of the list of rules for one or more primary regions and are available for failover of the respective primary regions. The regional management service can then deliver this information to a client. The regional management service can determine the primary regions that do not satisfy one or more of the rules from the list of rules for one or more primary regions and deliver this information to a client. The regional management service can perform automatic remediation and client remediation to the unavailable primary regions.

Managing primary region availability for implementing a failover from another primary region

The first computing system may interface with an operator of the application and a plurality of hosts of the application distributed between different partitions. The second and third computing systems may host first and second portion of the application in first and second partitions, respectively. The second and third computing systems may poll the first computing system to identify first and second value, respectively, representing state conditions of the first and second partitions, respectively, wherein the first and second partition state conditions are the active state, the passive state, and the fenced state. The second and third computing systems may receive responses from the first computing system comprising the first and second values, respectively, and based on the respective values, initiate a transition to the corresponding partition state condition. The first computing system may assign one of the first and second values to indicate which is the active state.

Systems and methods for enabling a highly available managed failover service

Managed multicast communications may be implemented across isolated networks. A virtual traffic hub may be implemented that connects different isolated networks. A control plane for the virtual traffic hub may accept requests to enable a multicast group between different isolated networks connected to the virtual traffic hub. The multicast group may then be enabled at the virtual traffic hub so that requests to add members to the multicast group and data packets directed to the multicast group can be handled according to multicast protocols by the virtual traffic hub.

Managed multicast communications across isolated networks

Systems and methods for managing requesting routing functionality associated with resource requests for one or more resources associated with a content provider are provided. The request routing functionality can correspond to the processing of domain name service ('DNS') requests for resources by computing devices and the resolution of the DNS requests by the identification of a network address of a computing device that will provide the requested resources. Based on the processing of DNS queries initiated by a client computing device, a CDN service provider can correlate client computing device identifiers, such as an Internet Protocol ('IP') address, with identifiers (e.g., IP addresses) associated with other components in a content delivery environment, such as DNS resolvers associated with the client computing device.

Managing request routing information utilizing client identifiers

Techniques for API-based endpoint discovery involving provider substrate extension resources are described. A discovery coordinator service located within the provider network can identify one or more endpoints from a set of potentially distributed endpoints for a client to utilize, where endpoints may be located within provider substrate extensions of the provider network. The discovery coordinator service can utilize location values of the client provided via an API request, such as its network address or geographic coordinates, to identify a nearby resource that may be most optimal for the client to use via providing minimal latency of access.

API-based endpoint discovery of resources in cloud edge locations embedded in telecommunications networks

Systems and methods for managing requesting routing functionality associated with resource requests for one or more resources associated with a content provider are provided. The request routing functionality can correspond to the processing of domain name service ('DNS') requests for resources by computing devices by correlating client computing device identifiers, such as an Internet Protocol ('IP') address, with identifiers (e.g., IP addresses) associated with other components in a content delivery environment, such as DNS resolvers associated with the client computing device. The processing of the DNS requests can also correspond to client computing device clustering or classes of client computing devices.

Request routing information based on client IP groupings

Growing community of inventors

Seattle, WA, United States of America

Colm MacCarthaigh