Amazon Technologies, Inc.

Ryan F Watson

Craig Wesley Howard

Bradley E Marshall

Harvo Reyzell Jones

Jonathan B Corley

Imran S Patel

Prashanth A Acharya

Lee B Rosen

Ronald James Snyder, Jr

John K Loendorf

Colm MacCarthaigh

Matthew Graham Baldwin

Douglas Stewart Laurence

Nathan Dye

Gregory Kenneth Truax

Alex Xiaoye Zhang

Chaitanya Ashok Solapurkar

Bennett Barnes Lynch

Systems and methods for processing a DNS query to identify and implement pre-processing information by a DNS server component in anticipation of a corresponding content request from a client computing device are provided. The pre-processing information can correspond to identification of content to be preloaded or other actions to be implemented by one or more computing devices in association with an anticipated client content request. Based on identification of the content or future actions, a DNS server component can provide the pre-processing information to one or more computing devices, such as computing devices of a CDN service provider and/or an original content provider, in advance of a corresponding request for content from the client computing device in order to improve performance associated with responding to the client request.

Processing DNS queries to identify pre-processing information

A system for quality of service management, including computing resources to provide services implemented at a provider network and network interfaces to establish a plurality of connections to perform tasks on behalf of clients. The system includes a quality of service (QOS) manager to determine respective client drop-off criteria indicating conditions for respective clients to cease communications via respective connections of the connections. The QoS manager also determines task information for respective tasks indicating a size of the respective tasks, a resource requirement for the respective tasks, or priority information for the respective tasks. The QoS manager further adjusts allocations of respective computing resources to the respective connections based on the respective client drop-off criteria and the task information. The QoS manager causes the respective computing resources to implement respective tasks on behalf of the clients according to the adjusted allocations.

Quality of service management for preventing client drop-offs

A data storage system having an intermediary server including an input interface, a memory and an output interface. The input interface configured to establish, via one or more programmatic interfaces, a connection with a client device to receive data for upload to a storage server and measure an input rate of the data received from the client device. The memory configured to store the data in a buffer as the data is received. The output interface configured to establish a connection with the storage server, determine an output rate for sending the data from the buffer to the storage server based at least in part on the input rate and a timeout value for the storage server, and send the data from the buffer to the storage server at the output rate.

Data transfer timeout management

Systems and methods are described to enable delivery of streaming content while inhibiting or preventing removal, blocking, or skipping of portions within that streaming content. A content delivery system can generate a manifest indicating content portions that form the streaming content. Each content portion can be identified in the manifest using a concealed identifier, which conceals the actual identifier of the content portion from the client to inhibit or prevent the client from automatically removing or modifying the content portion. On receiving a request for a content portion, the content delivery system can convert the concealed identifier into the actual identifier, and return the appropriate content portion to the client. In some instances, the specific identifiers included within a concealed manifest may be modified or adapted based on monitoring information of the client device, to ensure clients view given portions of streaming content.

Protecting content-stream portions from modification or removal

A system for scheduling transmission times to avoid connection timeouts includes a memory configured to store data in a buffer for upload to a storage system. The system also includes one or more computing devices configured to implement a connection manager. The connection manager is configured to establish a connection to a storage system. The connection manager is configured to iteratively repeat, until the data transfer operation is completed, begin transmitting the data from the buffer via the connection to the storage system, stop transmitting the data from the buffer via the connection to the storage system, where at least a portion of the data is retained in the buffer, determine a time to resume transmitting the data from the buffer via the connection to the storage system to avoid a connection timeout for the connection to the storage system, and wait until the time to resume.

Data transmission time management

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 computer implemented cache management system and method is provided for use with a service provider configured to communicate with one or more client devices and with a content provider. The system includes a cache hierarchy comprising multiple cache levels that maintain at least some resources for the content provider, and one or more request managers for processing client requests for resources and retrieving the resources from the cache hierarchy. In response to a resource request, the request manager selects a cache level from the cache hierarchy based on a popularity associated with the requested resource, and attempts to retrieve the resource from the selected cache level while bypassing cache level(s) inferior to the selected level.

Request management for hierarchical cache

An edge system receives requests from user devices to retrieves files from an origin server. Instead of retrieving the files as fast as possible, the edge system throttles the retrieval of files to a rate that just exceeds the speed at which the file is played by a browser or media player. The edge system determines an appropriate retrieval rate based on the contents of the file itself. For example, a manifest file associated with the file can indicate a time it takes to play back content and a bitrate of the content. Thus, the edge server can use this information to retrieve a file from an origin server at a rate that is just fast enough to minimize playback interruption. The retrieval rate determined by the edge server therefore does not rely on how fast or slow the user device retrieves the file from the edge server.

Adaptive transfer rate for retrieving content from a server

Systems and methods are provided for managing execution budgets for computing tasks in distributed computing systems. Execution budgets may include a budgeted number of operation retries that may be performed by the distributed computing system in response to failure of an operation. Execution budgets may also or alternatively include a budgeted amount of time in which the distributed computing system may perform the operations of a computing task. When a distributed computing system exhausts the execution budget allotted for a computing task, then further execution of the computing task or portions thereof may be terminated.

Distributed execution budget management system

Systems and methods are provided for managing computing tasks in distributed computing systems using execution budgets. Execution budgets may include a budgeted number of operation retries that may be performed by a distributed computing system in response to failure of an operation, or a budgeted amount of time in which the distributed computing system may perform the operations of a computing task. The configuration of the distributed system to execute the computing task may be generated based on prior consumption of execution budgets by portions of the computing system.

Growing community of inventors

Seattle, WA, United States of America

Ryan F Watson