Amazon Technologies, Inc.

Microsoft Technology Licensing, LLC

Dennis Tighe

Matthew Walters

Brian L Welcker

Tanmoy Dutta

Michael Anthony Hall

Conor Patrick Cahill

Cristian Marius Ilac

Grant Alexander Macdonald McAlister

Rebecca Claire Weiss

Christopher Richard Jacques De Kadt

Brad Eugene Marshall

Rui Wang

Sayantan Chakravorty

Akhilesh Mritunjai

Qun Guo

Barry Bailey Hunter, Jr

Nikita Pinski

David Charles Wein

Mark Ryland

Damian Gorman Wylie

Grant Alexander McAlister

Brian Mead Tyler

Mark Porter

Dean H Saxe

Peng Song

Rahul Nambiar

Bharath Subramanian Pichai

Jonathan Robert Hurd

Jerry Connolly

Carlos Alessandro Chiconato

Gokul Ramanan Subramanian

Gopal Ashok

Daniel Myers

Timothy Michael Galvin

Shawn McCoy

Khaled Sinno

Techniques for role-based permission delegation in a provider network. The techniques include an assuming service in the provider network sending a request to a temporary credential service in the provider network to assume a delegation role. The assuming service, acting in the delegation role, sending a request to the temporary credential service to assume the customer role in accordance with a down scoping policy. The assuming service, acting in the customer role, performing an action in a strict subset of actions on a customer resource. The techniques improve the operation of the provider network by allowing a permission to perform an action on the customer resource that is granted by the customer to a delegating service in the provider network to be delegated to the assuming service while complying with the access control principle of least privilege.

Role-based permission delegation in a provider network

A connection-based service impersonates request-based security for requests from clients that do not include credentials for the requests (e.g., data plane requests made via a connection-oriented security). A connection between a client and a connection-based service is established based on connection credentials that are based on security credentials from a request-based security service. The credentials are sent by a security component of the service to a local agent of the remote security service to be authenticated by the security service. An impersonation token is returned by the security service and cached by the local agent. Requests from the client to perform operations do not include credentials. For each request, the service passes an identifier for the client and the operation to a local authorization component that calls the agent for authorization of the requested operation. The agent uses the impersonation token to obtain authorization for the requested operation.

Impersonating request-based security in connection-based security environment

Quorum-based access control management may be implemented. Quorum controls may be created for determining whether to perform or deny access control operations to perform privileged tasks. When an access control operation is received, approval of the operation may be requested from members for the quorum control. If a policy for the quorum control is satisfied by approval responses, then approval to perform the access control operation may be provided.

Quorum-based access control management

A proxy server acts as an intermediary between a database client and a database server. The proxy server is configured with a set of user-defined rules. When a request is received from the database client, the proxy server may apply rules that modify, route, reject, log, or pass the request to the database server. Individual rules may be based on attributes of the client computer system, database server, or the request itself. In one embodiment, a rule may be used to translate a request from a format provided by the client into a format preferred by a destination database. In one embodiment, a rule may route a particular request to one of a number of databases based on the nature of the request.

Database proxy

Techniques for aggregating and emitting database activity record batches are described. Database activity records can be written to a shared memory queue and emitted to a destination using a remote procedure call (RPC). Individual database connection server processes can write client activity records to the queue. An activity monitor plugin in the database engine can monitor the audit records and aggregate the audit records into batches. Batches of audit records can be sent via RPC to their final or intermediate destination. Each instance host in a database service can include a client backend process configured to define how to submit audit records to shared memory. The activity monitor plugin can batch audit records in to messages and submit those messages via RPC to a security host manager and relaying response back to each relevant client backend.

Aggregating and emitting database activity record batches

A database proxy server provides a web service interface such as a representational state transfer ('REST') interface to a relational database. The proxy server maps a request submitted via the web service interface to a database interface. In some examples, the web service interface is a stateless REST interface that maps particular SQL statements or subroutines to a request submitted via a particular URL. A web client is able to pass parameters with a request using either URL encoding (the GET method) or within the body of the request (the POST method). The proxy server generates one or more database commands that correspond to the request. The database commands are submitted to the relational database, and the relational database performs the database commands to fulfil the request.

Database rest API

A proxy server acts as an intermediary between a database client and a database server. The proxy server establishes and maintains a set of logical connections to the database server. The proxy server receives a request from the database client, and generates a set of database commands that, when performed by the database server, are capable of fulfilling the request. The proxy server selects a particular logical connection from the set of logical connections based at least in part on a characteristic of the request, and submits the set of database commands to the database server via the selected particular logical connection. In various examples, the particular logical connection is selected so that various performance, efficiency, and security objectives are achieved.

Database proxy connection management

A proxy server receives requests from a client computer system and generates corresponding sets of database commands that are capable of fulfilling the requests when submitted to a database server. The proxy server may repeat processing associated with a particular request more than once under different operational conditions in order to improve future performance. In some examples, the proxy server submits a particular database command sequence to the database server using various operational parameters, and measures the performance of each submission to identify a particular set of operational parameters to be applied to the database server with future submissions. In another example, the proxy server determines a number of alternative command sequences that fulfill a particular request, and measures the performance of each of the alternative command sequences to determine how command sequences are generated for future requests.

Database command replay

Resources hosted in different virtualization platforms may be managed across the different virtualization platform. Requests to perform types of actions with respect to a resource hosted in a type of virtualization platform may be received. Mapping information between types of actions and actions available via interfaces for different types of virtualization platforms may be evaluated to select actions for an interface of the type of virtualization platform that hosts the resource. The selected actions may then be performed via the interface to perform the action with regard to the resource.

Managing hosted resources across different virtualization platforms

Systems and methods that supply changes on-the-fly and without breaking execution of codes for schema changes in a peer-to-peer environment. The modification component supplies changes to peers or nodes in a topology by initially identifying dependencies (e.g., multiple level) that can be affected by the schema change, followed by performing the schema change to the codes or stored procedures. Accordingly, dependencies in an entire system can be refreshed, wherein multiple levels of dependencies can exist.

Multiphase topology-wide code modifications for peer-to-peer systems

Growing community of inventors

Seattle, WA, United States of America

Dennis Tighe