Amazon Technologies, Inc.

Microsoft Technology Licensing, LLC

Panzura, Inc.

Other

Yun Lin

James Christopher Sorenson

David Carl Salyers

Shishir P Pardikar

Ankur Khetrapal

David C Steere

Nishanth Alapati

Navjot Virk

John Richard Taylor

Mohammed Samji

Brian Scott Aust

Rohan Kumar

Arun Sundaram

Venkataraman Ramanathan

Narasimha Rao S S Nagampalli

Sachin C Sheth

Shirish Koti

Steve Hyuntae Jung

David Matthew Kruse

David George De Vorchik

Balan Sethu Raman

Timothy P McKee

Jason Fergus Moore

Mark Joseph Cavage

Mihai Costea

Emanuel Paleologu

James Christopher Sorenson, Iii

Maxim A Ivanov

Ivan Brugiolo

Ramanathan Ganapathy

Eric Erwin Youngblut

Shishir Mondal

Danilo D'Amico Almeida

Ardis G Maison

Pradeep Vincent

Yi-Min Wang

Scott Field

Praerit Garg

Ahmed Hassan Mohamed

Richard James Sharpe

Jason L Cohen

Alexey A Polyakov

Nicholas Randall Waggoner

Jianrong Gu

Benjamin T Arai

Vincent R Orgovan

Gretchen L Loihle

Craig Boucher

Vinay Kumar Anneboina

Robert J Hensing, Jr

Jose Marcos De Oliveira

Satish Kumar Kotha

James Christopher Iii Sorenson

James Christopher Sorenson Iii

Methods, apparatus, and computer-accessible storage media for controlling export of snapshots to external networks in service provider environments. Methods are described that may be used to prevent customers of a service provider from downloading snapshots of volumes, such as boot images created by the service provider or provided by third parties, to which the customer does not have the appropriate rights. A request may be received from a user to access one or more snapshots, for example a request to export the snapshot or a request for a listing of snapshots. For each snapshot, the service provider may determine if the user has rights to the snapshot, for example by checking a manifest for the snapshot to see if entries in the snapshot manifest belong to an account other than the customer's. If the user has rights to the snapshot, the request is granted; otherwise, the request is not granted.

Methods and apparatus for controlling snapshot exports

A storage gateway serves as an interface between processes on a customer network and a service provider. The storage gateway is located on-premise with the customer processes. To customer processes, it appears that data is stored locally. However, the storage gateway interfaces with a remote storage service to store the data. For cached gateways, the primary data store is a remote data store, while frequently accessed data may be locally cached by the gateway. Reads may be satisfied from the local cache or from virtual data storage; writes are handled so as to appropriately update data blocks in the local cache and/or in virtual data storage. For shadowing gateways, the primary data store is the local data store; reads are passed through to a local data store, and writes are shadowed to virtual data storage as well as being sent to local data store.

Remote storage gateway management using gateway-initiated connections

Methods, apparatus, and computer-accessible storage media for providing redundant storage gateways. A client may create a storage gateway group and add storage gateways to the group. The client may assign one or more volumes on a remote data store to each the storage gateways in the group. Volume data for each storage gateway in the group may be replicated to at least one other storage gateway in the group. If one of the gateways in the group becomes unavailable, one or more other gateways in the group may take over volumes previously assigned to the unavailable gateway, using the replicated data in the group to seamlessly resume gateway operations for the respective volumes. Client processes that previously communicated with the unavailable gateway may be manually or automatically directed to the gateway(s) that are taking over the unavailable gateway's volumes.

Redundant storage gateways

Methods, apparatus, and computer-accessible storage media for providing a volume-based block storage service and application programming interfaces (APIs) to the service. A block storage service and block storage service APIs may allow processes (applications or appliances) on the service client network to leverage remote, volume-based block storage provided by the service provider. The APIs may provide a standard interface to volume-based block storage operations on a remote data store. The service provider, the service clients, and/or third parties may develop various applications and/or appliances that may, for example, be instantiated in service clients' local networks and that leverage the block storage service via the APIs to create and manage volumes and snapshots on the remote data store and to upload and download data from the volumes and snapshots on the remote data store.

Service and APIs for remote volume-based block storage

Remote storage gateway shadow or cache configuration

Methods, apparatus, and computer-accessible storage media for optimizing block storage I/O operations in a storage gateway. A write log may be implemented in a block store as a one-dimensional queue. A read cache may also be implemented in the block store. When non-ordered writes are received, sequential writes may be performed to the write log and the data may be written to contiguous locations on the storage. A metadata store may store metadata for the write log and the read cache. Reads may be satisfied from the write log if possible, or from the read cache or backend store if not. If blocks are read from the read cache or backend store to satisfy a read, the blocks may be mutated with data from the write log before being sent to the requesting process. The mutated blocks may be stored to the read cache.

Methods and apparatus for block storage I/O operations in a storage gateway

The disclosed embodiments disclose techniques for maintaining global name consistency for a distributed filesystem. Two or more cloud controllers collectively manage distributed filesystem data that is stored in one or more cloud storage systems; the cloud controllers ensure data consistency for the stored data, and each cloud controller caches portions of the distributed filesystem. During operation, a cloud controller receives a client request to perform a namespace operation upon a filesystem object. The cloud controller contacts the cloud controller that manages ('owns') the portion of the global namespace for the distributed filesystem that includes the filesystem object. This second cloud controller ensures the consistency of the filesystem object across the distributed filesystem during the namespace operation.

Maintaining global namespace consistency for a distributed filesystem

Methods, apparatus, and computer-accessible storage media for shadowing data stored on a local store to a remote store provided by a service provider. A gateway may be configured as a shadowing gateway on a customer network in response to receiving configuration information. The shadowing gateway may receive reads and writes to the local store. The gateway passes the requests to the local store, and also uploads write data indicated by the writes to the service provider to update a snapshot of the local store maintained by the service provider on the remote store. The write data may be buffered to a write log for uploading, and may be uploaded as blocks according to a block storage format used by the service provider. The shadowing process may be transparent to processes on the customer network. The shadowed data may be used to recover data on the local store.

Shadowing storage gateway

The disclosed embodiments disclose techniques for sending interim notifications to clients of a distributed filesystem. Two or more cloud controllers collectively manage distributed filesystem data that is stored in one or more cloud storage systems; the cloud controllers ensure data consistency for the stored data, and each cloud controller caches portions of the distributed filesystem. During operation, a cloud controller receives a client request to perform a namespace operation upon a filesystem object. The cloud controller determines that it will need to contact at least one of another peer cloud controller or a cloud storage system to service the request, and sends an interim notification to the client to notify the client that the request is pending.

Sending interim notifications for namespace operations for a distributed filesystem

The disclosed embodiments disclose techniques for managing opportunistic locks in a distributed filesystem. Two or more cloud controllers collectively manage distributed filesystem data that is stored in the cloud storage systems; the cloud controllers ensure data consistency for the stored data, and each cloud controller caches portions of the distributed filesystem. During operation, a client sending a request to access a file from a cloud controller also requests an opportunistic lock for the file. If there are no other outstanding client accesses on the other cloud controllers that preclude the requested opportunistic lock, the cloud controller grants the client file access and the opportunistic lock.

Managing opportunistic locks in a distributed file system

The disclosed embodiments disclose techniques for managing consistency for a file in a distributed filesystem. Two or more cloud controllers collectively manage distributed filesystem data that is stored in the cloud storage systems; the cloud controllers ensure data consistency for the stored data, and each cloud controller caches portions of the distributed filesystem. During operation, a cloud controller receives from a client a request to access the file. The cloud controller determines a level of consistency that is associated with the file, and then uses this level of consistency to determine whether to communicate with a peer cloud controller when handling the request.

Managing the level of consistency for a file in a distributed filesystem

Growing community of inventors

Bellevue, WA, United States of America

Yun Lin