Amazon Technologies, Inc.

Lalit Jain

Sandeep Kumar

Danny Wei

Arvind Chandrasekar

Marc Stephen Olson

Sriram Venugopal

James T Pinkerton

Varun Verma

Kristina Kraemer Brenneman

Oscar Allen Grim Courchaine

Manu Anand

Ankit Singh

Visakh Sakthidharan Nair

Pavan Kumar Korlepara

Aman Singhal

Ajit Balachandran

Kumar Shubhankar

Generally described, one or more aspects of the present application correspond to techniques for creating encrypted block store volumes of data from unencrypted object storage snapshots of the volumes. These encryption techniques use a special pool of servers for performing the encryption. These encryption servers are not accessible to users, and they perform encryption and pass encrypted volumes to other block store servers for user access. The encryption context for the volumes can be persisted on the encryption severs for as long as needed for encryption and not shared with the user-facing servers in order to prevent user access to encryption context.

Encryption by default in an elastic computing system

Aspects relate to a framework for utilizing a single API request to manage the creation of consistent snapshots for a set of volumes attached an individual instance in a distributed computing environment. Responsive to receipt of an API request identifying the instance, the multi-volume snapshot service identifies a set of volumes attached to the identified instance. The identified set of volumes can be processed or filtered to eliminate specific volumes or types of volumes, such as boot volumes. In the event that any snapshot creation attempt fails, the multi-volume snapshot service fails the API request and can delete any snapshot data generated prior to the failure.

Crash-consistent multi-volume backup generation

Generally described, one or more aspects of the present application correspond to techniques for creating multiple encrypted block store volumes of data from an unencrypted source. These encryption techniques can use a transform fleet as an intermediary use between the unencrypted source and the encrypted volumes. The transform fleet can obtain data of the volume from one or both of two sources&#x2014;an object storage 'snapshot' a block storage 'source volume'&#x2014;and can then apply the appropriate encryption key for performing the encryption of a particular volume.

Creating multiple encrypted volumes from a single source

Generally described, one or more aspects of the present application correspond to techniques for modifying volume encryption status, either by creating an encrypted copy of an unencrypted source volume or by re-encrypting the replica with a different key than the source volume. This can be accomplished using an intermediary transform fleet that stores the encryption key(s) and performs encryption (and decryption, in cases where the source is encrypted). Further, these techniques can implement a state refresh for any client attached to the volume in order to equip the client to handle the different encryption state of the encrypted volume.

Encryption intermediary for volume creation

A client-configurable tiering service implements an interface allowing a client to specify a tiering policy selected from a plurality of supported tiering policies for data of the client stored in a warm tier, wherein the tiering policies specify conditions for relocating portions of the data to a cold tier. The interface also allows a client to specify a tombstone forwarding policy selected from a plurality of supported tombstone forwarding policies, wherein the tombstone forwarding policies specify how data relocated from the warm tier to the cold tier is subsequently retrieved in response to an access request directed to the warm tier. The client-configurable tiering service relocates and retrieves data between a warm tier and a cold tier in accordance with the client's selected policies. In some embodiments, a client may specify further aspects of how data is stored and relocated between different tiers of a data store.

Client-configurable data tiering service

Growing community of inventors

Seattle, WA, United States of America

Lalit Jain