Amazon Technologies, Inc.

Emc Corporation

Benjamin Tillman Farley

Gregory Branchek Roth

Benjamin Elias Seidenberg

Ari Juels

Gregory Alan Rubin

Graeme David Baer

Kevin Bowers

Michael Mansfield Swift

Petr Praus

Aleksandrs J Rudzitis

John Kenneth Beer

Leandro Batista Lameiro

Christine Marie Gerpheide

Sreekumar Mukundan Pisharody

Venkatanathan Varadarajan

Thomas Ristenpart

Electronically signed data is persistently stored in data storage. After the passage of time, the data may be accessed and presented to a trusted entity for verification of the data. The trusted entity may have access to secret information used to sign the data. The trusted entity may use the secret information to verify an electronic signature of the data. One or more actions may be taken based at least in part on a response provided by the verification system.

Trusted data verification

Method and systems are disclosed for providing a function as a service for an application. The application may comprise an email application. A user may define or select an application codes set for performing a specific functionality. The user may define rules that associate specific events with execution of the application code set. Upon detection of an event, a condition may be checked associated with the application. If the condition is satisfied, the application code set may be caused to be executed. The application code set may modify data, such as an email message.

User defined application code for electronic mail

A network-based service for the management of cryptographic key, such as a key management service ('KMS'), provides a web service application programming interface ('API'). Cryptographic keys managed by the service may be stored in a one or more network-connected cryptographic devices such as network-connected hardware security modules (&#x201c;HSM&#x201d;). The key management service maintains metadata associated with the cryptographic keys. When a request is received by the key management service, the key management service uses an identifier provided with the request to identify metadata associated with a cryptographic key used to fulfill the request. The key management service uses the metadata to identify a cryptographic device containing the cryptographic key. The key management service generates a set of commands for fulfilling the request such that the commands are compatible with a protocol implemented by the identified cryptographic device, and the set of commands are sent to the identified cryptographic device.

Key management and hardware security integration

A computing resource service receives a request. In response to the request, the computing resource service queries a probabilistic data structure for an entry corresponding to the request. The computing resource service obtains, from the probabilistic data structure, a value that corresponds to the entry. Based at least in part on this value, the computing resource service determines whether the entry has expired. If the entry is expired, the request is fulfilled. However, if the entry has not expired, the request is denied.

Expiration of elements associated with a probabilistic data structure

Technologies are disclosed herein for epoch-based expiration of temporary security credentials. A temporary security credential is issued that identifies one or more epochs and that specifies one or more versions of the identified epochs during which the temporary security credential is valid. The temporary security credential may then be utilized to request access to another system, service or component. In order to determine whether such a request may be granted, current epoch versions for the epochs identified in the temporary security credential are obtained. The current epoch versions for the identified epochs are then compared to epoch versions specified in the temporary security credential to determine if the request can be granted. The current epoch versions may be periodically modified in order to expire previously issued temporary security credentials. A temporary security credential might also specify an expiration time after which the temporary security credential is no longer valid.

Epoch-based management of security credentials

A method includes the step of running a set of instances on at least one cloud for a first time interval, each of the instances comprising a bundle of virtualized resources. The method also includes the step of evaluating one or more performance characteristics of each of the instances in the set of instances over the first time interval. The method further includes the step of determining a first subset of the set of instances to maintain for a second time interval and a second subset of the set of instances to terminate for the second time interval responsive to the evaluating step. The steps are performed by at least one processing device comprising a processor coupled to a memory.

Determining instances to maintain on at least one cloud responsive to an evaluation of performance characteristics

Growing community of inventors

Seattle, WA, United States of America

Benjamin Tillman Farley