Amazon Technologies, Inc.

Christopher Richard Jacques De Kadt

James Alfred Gordon Greenfield

Eric Jason Brandwine

Allan Henry Vermeulen

David Everard Brown

Marc John Brooker

Marc J Brooker

Kevin Ross O'Neill

Mark Joseph Cavage

John Michael Morkel

Marvin Michael Theimer

Tate Andrew Certain

Timothy Daniel Cole

Yannis Papakonstantinou

Matthew Scott Garman

Abhinav Agrawal

Robin Alan Golden

Yevgeniy Mikhaylyuta

Cornelle Christiaan Pretorius Janse Van Rensburg

Gustav Karl Mauer

Arjun Radhakrishnan

Gregory Branchek Roth

Jacob Adam Gabrielson

Jacob Carr

Benjamin Tobler

Jean-Paul Bauer

Benjamin Van Der Merwe

Jacobus Johannes Nicolaas Van Der Merwe

Dirk Gerhardes Oberholster

Adi Meyers

Randall Avery Shealey

David R Richardson

Peter Nicholas Desantis

Marcin Piotr Kowalski

Roland Alexander Paterson-Jones

Matthew James Eddey

Mathew Daniel

Carlos Vara Callau

André Mostert

Sebastian Martin Biemueller

Marc Andrew Bowes

Thomas Friebel

Rohit Kulshreshtha

Christopher Anthony Romanzin

Willem Visser

Methods and apparatus for portable network interfaces to manage authentication and license enforcement. A system may include a plurality of resource instances including a producer instance configured to implement a network-accessible service, and an authentication coordinator. The coordinator may assign an interface record to the service, wherein the interface record comprises an IP address and a set of security properties. The coordinator may configure the security properties to allow a client to request an attachment of the interface record to a selected resource instance, such that the selected resource instance is enabled to transmit network messages from the IP address using one or more physical network interfaces of the selected resource instance. The producer resource instance initiates authentication operations for the service, including at least one authentication operation based on the IP address of the interface record.

Portable network interfaces for authentication and license enforcement

A database management system stores data for a table as a journal of transaction. The records of the journal comprise information indicative of changes applied to a document of the table. The database receives a query on a table of transactions performed on the table. In response to the query on the table of transactions, the database generates results by retrieving and projecting the records of the journal in accordance with the query. The results of the query are indicative of changes applied to the document of the table.

Journal queries of a ledger-based database

A journaled database system may comprise data nodes that maintain a collection of data and provide read access to the data to a client in accordance with a read schema and write access to the client in accordance with a write schema. A change to the schemas may be proposed. A materialization schema may be identified based on correlated determinations that both of the read schema and the write schema are satisfiable based on the materialization schema. The proposed changes may be accepted when the read schema and write schema are simultaneously satisfiable.

Transaction pipeline materialization schemas

A journaled database system may comprise data nodes that collectively maintain a collection of data and provide clients with read and write access to the collection. Correlated classification functions may be associated with read and write operations, such that items affected by a write operation are classified similarly to items accessed during a read operation. Read and write signatures may be formed based on the classification. Conflicts may be detected by comparing the read and write signatures for equivalent or overlapping classifications.

Extended query families

A database management system receives a request to perform a transaction. The database management system commits the transaction, and in response to committing the transaction, generates a cryptographic hash based on an attribute of the transaction. The cryptographic hash is stored in a leaf-region of a hash tree. In response to a request to verify the transaction, signatures are retrieved from the tree based on a traversal of the tree to locate the node corresponding to the transaction. The retrieved signatures are used to verify the transaction.

Cryptographic verification of database transactions

A database management system stores data for a table using a ledger which comprises journal and summary portions. A query processor of the database identifies a first set of operations to update a document of a table in accordance with an update command. The query processor identifies a second set of operations to update tables or views that are potentially affected by the update to the document. The query processor then causes the first and second sets of operations to be executed as an atomic unit.

Index and view updates in a ledger-based database

Methods and systems for provisioning computing resource instances among implementation resources based on trust to reduce interference between computing resource instances implemented by the same implementation resources. In an embodiment, a trust rating is determined for a computing resource instance based at least in part on one or more trust factors. The suitability of an implementation resource to implement the given computing resource instance may be evaluated based at least in part on the trust rating of the computing resource instance and a trust rating of the implementation resource. In some embodiments, the trust rating of the implementation resource may be predefined or based on trust ratings of computing resource instances that are currently implemented by the implementation resource. An implementation resource may be selected to implement the computing resource instance based at least in part on its suitability thus determined.

Trust-based resource allocation

Users intending to launch instances or otherwise access virtual resources in a multi-tenant environment can specify a launch configuration. For each type of instance or each type of user, at least one launch configuration is created that includes parameters and values to be used in instantiating an instance of that type, the values being optimized for the current environment and type of instance. Launch configurations can be optimized for different types of users, such as to account for security credentials and access levels. Such an approach enables users to launch instances by contacting the resource provider directly without need for a proxy, which can function as a choke point under heavy load. The use of an appropriate launch configuration can be enforced for any type of user at any level, such as at the sub-net level, by modifying a request that does not specify an appropriate launch configuration.

Enforceable launch configurations

A database management system receives a request to create an index for a virtual view of a database table. In response to the request, the database management system identifies relationships between the columns of the virtual view and columns of the database table. The database management system generates an index on the database table, where columns are included in the generated index based on the identified relationships and the definition of the virtual view. Queries of the virtual view are assisted by the generated index of the underlying table.

Indexes on non-materialized views

A journaled database may comprise a computing node that forms a local version of a global state, synchronized with respect to the high-water mark of a data node that maintains the global state. Instructions to modify the state that have been committed, subsequent to forming the local version of the state, may be represented in a merge signature. An uncommitted transaction may be checked for conflicts with respect to a last-ordered committed instruction to modify the data state. Validation with respect to earlier instructions represented by the merge signature may be skipped.

Transaction pipelining in a journaled database

Technologies are disclosed for improving the availability of a distributed application by computing scores for the application that indicate the extent to which the configuration of hosts implementing the application complies with best practices for maximizing availability. One score can be generated for the application based upon the physical location of the hosts used to implement the application and the components upon which the application is dependent. Another score can be generated for the application based upon the number of data centers that hosts executing the application are located in as compared to a minimum required number of data centers. Another score can be generated for the application based upon the distribution of hosts utilized to execute the application across data centers. Operations can be initiated for improving the scores, such as migrating a host to a new rack or server, or migrating a host to a different data center.

Availability of a distributed application using diversity scores

Systems, methods and computer-readable media are described for pre-warming compute instances in datacenters. A service provider associated with the datacenters may expect a demand for the compute instances and pre-configure computing resources within the datacenters to pre-launch the compute instances. As such, when a user requests a compute instance, the service provider may satisfy the request by allocating a pre-warmed compute instance to the user.

Pre-configure and pre-launch compute resources

Growing community of inventors

Cape Town, South Africa

Christopher Richard Jacques De Kadt