Amazon Technologies, Inc.

Nathan Dye

Harvo Reyzell Jones

Craig Wesley Howard

Anton Stephen Radlein

Jacob Adam Gabrielson

Colm MacCarthaigh

Brian L Barker

Bradley E Marshall

Jonathan B Corley

Ryan F Watson

Imran S Patel

Narjala Prakash Bhasker

Prashanth A Acharya

Lee B Rosen

Ronald James Snyder, Jr

John K Loendorf

Mikhail Ivanovich Golovnykh

Jonathan A Jenkins

Brett Richard Taylor

Marcin Piotr Kowalski

Alec Peterson

Lee Atkinson

Rich Vorwaller

Robert Martin Wise

Ryan Waters

A real-time data validation system prevents problematic updates from being replicated from a primary database to a replica database. The data validation system may inject a time delay into the replication process, so that when an update in a replication stream fails a specified data validation, the data validation system will prevent the update from being applied to the replica. The replication process may be halted to take snapshot of the replica database during the halt, and resumed after the snapshot. Accordingly, if the problematic update is later confirmed to be invalid, the replica database can be rolled back to a point before the problematic update. Advantageously, the disclosed system can be used to implement a variety of data validations on top of a database replication process to protect the replica database from receiving undesired updates.

Real-time data validation using lagging replica databases

A computing system that receives and stores configuration information for the application in a data store. The configuration information comprises (1) identifiers for a plurality of cells of the application that include at least a primary cell and a secondary cell, (2) a defined state for each of the plurality of cells, (3) one or more dependencies for the application, and (4) a failover workflow defining actions to take in a failover event. The computing system receives an indication, from a customer, of a change in state of the primary cell or a request to initiate the failover event. The computing system updates, in the data store, the states for corresponding cells of the plurality of cells based on the failover workflow and updates, in the data store, the one or more dependencies for the application based on the failover workflow.

Systems and methods for enabling a highly available managed failover service

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

a computing system that receives and stores configuration information for the application in a data store. The configuration information comprises (1) identifiers for a plurality of cells of the application that include at least a primary cell and a secondary cell, (2) a defined state for each of the plurality of cells, (3) one or more dependencies for the application, and (4) a failover workflow defining actions to take in a failover event. The computing system receives an indication, from a customer, of a change in state of the primary cell or a request to initiate the failover event. The computing system updates, in the data store, the states for corresponding cells of the plurality of cells based on the failover workflow and updates, in the data store, the one or more dependencies for the application based on the failover workflow.

Techniques are described for providing service availability zones for computing-related services provided by a cloud provider network. According to some embodiments, the use of service availability zones enables users to achieve greater availability assurance for workloads sensitive to downtime or outages. The sensitivity of such workloads to downtime may be due to financial, regulatory, safety, or other reasons. Such availability-sensitive applications may in some cases be configured to run in multiple regions of a cloud provider network to increase their availability compared to running in a single availability zone. However, for some applications, the implementation of an application across multiple regions may not be feasible or desirable. The use of service availability zones provides user-visible fault domains within a single region of a cloud provider network, thereby enabling users to readily and reliably achieve application layer availability of approximately 99.999% for a service within a single region.

Service availability zones for high availability workloads

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

a data store and a proxy system. The data store may store state data relating to a cell of the application, each cell having a state. The proxy system may identify whether the cell is operating in the active state, the passive state, or the fenced state and access a database of acceptable and unacceptable commands for the cell's state. For each request directed to the cell received, the proxy system may identifies the request as an acceptable request based on identifying that one or more commands of the request are acceptable to process in the cell's state or identifies the request as an unacceptable request based on identifying that one or more commands of the request are unacceptable to process in the cell's state. The proxy system then conveys the acceptable requests and unacceptable requests appropriately.

Systems and methods are disclosed to implement a real-time data validation system that prevents problematic updates from being replicated from a primary database to a replica database. In embodiments, the data validation system injects a time delay into the replication process, so that when an update in a replication stream fails a specified data validation, the data validation system will prevent the update from being applied to the replica. In embodiments, the replication process is halted, a snapshot of the replica database is taken during the halt, and replication to the replica is resumed. Accordingly, if the problematic update is later confirmed to be invalid, the replica database can be rolled back to a point before the problematic update. Advantageously, the disclosed system can be used to implement a variety of data validations on top of a database replication process to protect the replica database from receiving undesired updates.

Methods and apparatus for content preloading using predictive models are disclosed. A system includes computing devices that generate a model to determine a predicted set of additional network content assets anticipated to be requested by a client after the client has requested a given set of assets. The devices determine, based on characteristics of a client's content request, whether to initiate an asset preload operation using the model. If a decision is made to initiate an asset preload, the devices identify, using the model, the predicted set of assets corresponding to the request, and initiate delivery of at least a portion of the predicted set to one or more destinations on behalf of the client.

Content preloading using predictive models

Techniques are described for managing cached data in a network environment. In one example, the techniques include receiving a client request for a data group, determining that a cached copy of the requested data group that is stored in the persistent cache storage is no longer valid relative to a current copy of the data group stored at a remote data source system, obtaining from the remote data source system information about differences between the cached copy and the current copy and instructions associated with the identified differences, modifying, by the configured server computing system, the cached copy to include the identified differences in accordance with the received instructions, and providing, by the configured server computing system, the modified cached copy of the requested data group to the client in response to the client request.

Managing cached data in a network environment

Systems and methods are described that enable the mitigation of network attacks directed to specific sets of content on a content delivery system. A set of content targeted in the attack may be identified based at least in part on a combination of network addresses to which attacked-related packets are transmitted. Thereafter, the content delivery system may mitigate the attack based on the identified target. For example, where both targeted and non-targeted sets of content are associated with the attacked network addresses, traffic directed to these sets of content may be separated, e.g., in order to reduce the impact of the attack on the non-targeted sets of content or increase the computing resources available to the targeted content. Redirection of traffic may occur using either or both of resolution-based redirection or routing-based redirection.

Growing community of inventors

Seattle, WA, United States of America

Nathan Dye