Amazon Technologies, Inc.

Rachit Jain

Conor Patrick Cahill

Varun Jayant Oswal

Praveen Akinapally

Rohit Raj

Brigid Ann Johnson

Ian Leung

Liam Simon Hewitt

Ian Man Hin Leung

Jasmeet Chhabra

Dmitry Frenkel

Harshad Vasant Kulkarni

Ankit Kumar

Munjal Doshi

Luke Edward Kennedy

Dan Popick

Per Mikael Horal

Ritwick Dhar

Sandesh Sanjeev

Andrew Oppenlander

Yijia Lu

Ankur Agarwal

Sulay Shah

Sharad Sridhar

Douglas Spencer Hewitt

Ogbeide Derrick Oigiagbe

Lennart Christopher Leon Kats

Julian Eric Naydichev

Managed lifecycle roles are disclosed. Managed lifecycle roles may be used for secure credential vending or otherwise. For instance, an entity (e.g., administrator or other entity) requests, via an interface of a role manager, creation of a role associated with a lifecycle definition (e.g., an expression of an enforceable expiration of the role or similar characteristic). The role manager stores the role and role lifecycle definition to a data store. Another entity requests to use the role to perform some operation with respect to a resource. A credential service validates the request against a lifecycle definition for the role (and against an access control list, in some examples) and responds to valid requests with credentials useable to perform the operation with respect to the resource. The other entity uses the credentials to perform the operation with respect to the resource. A sweep process manages attributes of the roles.

Managed lifecycle roles for secure credential vending

An Identity and Access Management Service implements persistent source values PSVs) for assumed identities. A source value (e.g., an original identifier of an entity) is persisted across assumed identities, facilitating identification of entities (users or applications) responsible for actions taken by the assumed (e.g., alternative) identities. The Manager receives a request to assume an identity. The request includes the entities current credentials and a PSV. The current credentials are authenticated and a persistent source value policy may be relied on to determine whether and/or how to grant the assumed identity. The PSV may be copied from credentials in the request in order to be included in the credentials for the requested identity that the Manager provides in response to the request. Use of the requested credentials, including the PSV, to access services or resources may be logged, the logs including the PSV from the request to assume the identity.

Persistent source values for assumed alternative identities

A recovery workflow is part of an automated management service for bare metal hosts allocated for single-tenant operation in a multi-tenant environment. The health of the hosts is monitored using a set of health criteria. If it is detected that one of the host machines fails a health check then a host recovery workflow can be initiated. As part of the workflow, the failed host can be repurposed or retired. A spare host class can be used to obtain a new host to take over for the failed host. Once deployed, the operation of the new host can be tested. Upon passing the test, the new host can take over for the failed host. A new host resource can be automatically requested to be added to the spare host class in order to ensure that there are sufficient resources available in case of an additional failure.

Automated host management service

Features are disclosed for managing multiple hosts that stream sequential data to nodes for propagation. The hosts can include a primary host and a failover host that each store a replica of the sequential data. A computing device can monitor the hosts and identify the occurrence of a failover event for the primary host. For example, the computing device may determine the schema has been modified. The computing device can further determine to failover to the failover host based on the failover event. The computing device can insert a flip task into the stream of sequential data for the primary host. The insertion of the flip task may be automatic. Further, each node reading from the stream of sequential data for the primary host may encounter the flip task and failover to the failover host at the same logical position but a different absolute position.

Managing failover between data streams

The present disclosure relates to generating a passphrase for an encrypted volume by at least cryptographically combing the first cryptographic key and the shared secret. Where the shared secret is split into a plurality of shares and a first number of the plurality of shares is greater than a second number of the plurality of shares and the second number of the plurality of shares is required to reconstruct the shared secret.

Securing encrypted volumes in a distributed environment

Techniques for managing permissions to cloud-based resources with session-specific attributes are described. A first request to create a first session to permit access to resources of a provider network is received under an assumed role. The first request is permitted based on an evaluation of a rule associated with the role. Session data including a user-specified attribute included with the first request is generated. A second request to perform an action with a resource hosted by the provider network is received. The user-specified attribute is obtained from the session data based at least in part on the second request. The second request is permitted based on an evaluation of another rule with the user-specified attribute.

Managing permissions to cloud-based resources with session-specific attributes

Restoring data to a data store that suffered corrupted data over a time period is disclosed. A system may provide an interface to specify a time window and filter conditions for identifying corrupted data in an object in a data store, such as, but not limited to, a corrupted NoSQL table. Corrupted data is identified by applying the filter conditions to change logs for the data object (e.g., the No SQL table) in the data store. Repair operations are determined for individual items identified via the filter conditions. Identified corrupted data for items may be corrected, from change logs or backup data in some instances (e.g., data may be deleted, or updated or replaced with data from a backup of the data store when necessary).

Restoration of a data source

Transitive restrictions can be applied to requests received on a session. A session token can be issued for an active session, and a transitivity setting specified to indicate the types of requests for which the transitive restriction is to be enforced. This can include enforcing the restriction on requests received from outside a trusted environment, requests within a scope of enforcement, or enforcing the restriction at request authentication. Any request received from an untrusted source that fails to satisfy the transitive restriction will be denied. Requests from inside the trusted environment may not have the transitive restriction enforced, such as where a new token is issued. This enables services within the environment to make calls on behalf of the customer, while ensuring that third parties obtaining the session token cannot successfully initiate such calls.

Restriction transitivity for session credentials

A security token service receives a request for a token. The request indicates a set of access control policies that define a set of permissions for access to a resource. The security token service generates the token to comprise a set of identifiers of the set of access control policies. The security token service provides the token in response to the request to enable the token to be used to access the resource in accordance with the set of access control policies.

Policy implementation using security tokens

Systems and methods for manage throttling limits in a distributed system are disclosed herein, according to some embodiments. A system includes a plurality of server nodes to perform a service. The system includes one or more processors a memory. The memory stores instructions that, when executed by the one or more processors, cause the one or more processors to perform operations. The operations include receiving a request for the service. The operations also include calculating whether accepting the request would exceed a service throttling limit for the plurality of server nodes for the service and whether accepting the request would exceed a node throttling limit for a server node of the plurality of server nodes. The operations also include accepting the request for processing at the server node responsive to calculating that the service throttling limit and the node throttling limit would not be exceeded.

Growing community of inventors

Bothell, WA, United States of America

Rachit Jain