Abstract: A storage controller is implemented for controlling a storage system. The storage controller may be implemented using a distributed computer system and may include components for servicing client data requests based on the characteristics of the distributed computer system, the client, or the data requests. The storage controller is scalable independently of the storage system it controls. All components of the storage controller, as well as the client, may be virtual or hardware-based instances of a distributed computer system.

Abstract: A storage management system monitors an indicator of whether data storage is capable of meeting a performance description as stored on a current implementation resource, such as a storage server. The indicator may be used to determine whether none, some or all of the data storage should be moved from the current implementation resource to an available implementation resource.

Abstract: A system and method for optimizing the performance of one or more disks in a storage array in response to access requests by other computer devices and processes across a network. For requests to access to the storage disk from the network, such as a read/write request, a response monitor notes the service time for each access requests by the storage disk, and if the performance in handling the access requests fails to meet, at least, a predetermined time threshold, actions can be taken to migrate data, modify accesses permitted to the disk, or otherwise indicate underperformance.

Abstract: Systems and methods for managing credentials distribute the credentials to subsets of a set of collectively managed computing resources. The collectively managed computing resources may include one or more virtual machine instances. The credentials distributed to the computing resources may be used by the computing resources to perform one or more actions. Actions may include performing one or more functions in connection with configuration, management, and/or operation of the one or more resources, and/or access of other computing resources. The ability to use credentials may be changed based at least in part on the occurrence of one or more events.

Abstract: A system for allocating constrained resources (e.g., downstream services, execution threads, database connections, input/output channels, computational resources, and/or memory) to requested services that are dependent on those resources may include multiple resource queues, each of which maintains a queue of requests for a respective constrained resource, and multiple service request queues, from which requests may be subsequently serviced. As each request reaches the head of a resource queue, it may receive a resource token for a respective constrained resource. Once the request has collected resource tokens for each of the constrained resources on which it depends, the request may be passed to a service request queue that maintains a queue of requests of a particular type. Requests in the multiple service request queues may be serviced on a round-robin or weighted round-robin basis. The number of tokens available for each constrained resource may be modified based on observed system performance.

Abstract: A storage management system monitors an indicator of durability of a dataset hosted by a current implementation resource, such as a storage server. The indicator may be used to determine whether none, some or all of the data storage should be moved from the current implementation resource to an available implementation resource.

Abstract: Systems, methods and related processes for securely erasing and/or rendering permanently inaccessible data stored on storage systems securely erased is described. Such storage systems may, in some aspects, integrate hardware capable of secure erasure. In some aspects, a cryptographically-based system is utilized.

Abstract: A data storage device is modified or adapted to support the storage and retrieval of versioned data sets. In some embodiments, the modified or adapted data storage device is capable of writing and tracking multiple data sets per logical location, and is capable of retrieving a specific versioned data set upon receiving a read request for that version of the data set.

Abstract: The relative health of data storage drives may be determined based, at least in some aspects, on data access information and/or other drive operation information. In some examples, upon receiving the operation information from a computing device, a health level of a drive may be determined. The health level determination may be based at least in part on operating information received from a client entity. Additionally, a storage space allocation instruction or operation may be determined for execution. The allocation instruction or operation determined to be performed may be based at least in part on the determined health level.

Abstract: A data volume may be shelved based at least in part on statistical triggers associated with the data, a user of the data, or a system configured to store and/or manage the data. Upon receiving a request to detach a data volume from a computing device, a determination of whether the data volume should be shelved may be made. In some aspects, the data volume may be shelved by moving the data to another storage system, storing an identifier of the data volume, and de-allocating space associated with the shelved data such that the shelved data is no longer maintained in the storage system. Further, in some aspects, upon a request to attach the data volume, the data may be moved back, the original identifier may be re-assigned to the data volume, and the data volume may be re-attached to the computing device.

Abstract: A system and method for predicting the likelihood of failure of the individual sectors of a magnetic storage disk based upon the monitoring of adjacent sector performance in responding to access requests. The prediction for a specific target sector's fidelity can be made through the gathering of sector performance data that occurs during normal read/write actions to the adjacent sectors, without a recent access request necessarily being made to the target sector. Scrubbing of the sectors can also be directed based upon the needed sector access data for target sector fidelity prediction.

Abstract: The relative health of data storage drives may be determined based, at least in some aspects, on data access information and/or other drive operation information. In some examples, upon receiving the operation information from a computing device, a health level of a drive may be determined. The health level determination may be based at least in part on operating information received from a client entity. Additionally, a storage space allocation instruction or operation may be determined for execution. The allocation instruction or operation determined to be performed may be based at least in part on the determined health level.

Abstract: A system and method for optimizing the performance of one or more disks in a storage array in response to access requests by other computer devices and processes across a network. For requests to access to the storage disk from the network, such as a read/write request, a response monitor notes the service time for each access requests by the storage disk, and if the performance in handling the access requests fails to meet, at least, a predetermined time threshold, actions can be taken to migrate data, modify accesses permitted to the disk, or otherwise indicate underperformance.

Abstract: An I/O scheduler can manage and schedule write requests that are sent to a storage device in order to prevent the write requests from dominating a storage buffer of the storage device. The I/O scheduler can monitor the number of I/O requests in the storage buffer and maintain a balance between write requests and read requests in the storage buffer. The I/O scheduler monitor the latency of the storage device in processing write requests and manage the write requests sent to the storage device based on the latency. The I/O scheduler can utilize one or more write thresholds. The write thresholds can define thresholds of the number of write requests in the storage buffer and thresholds for the latency of the storage device in processing write requests. The write threshold can represent acceptable levels of write request in the storage buffer and acceptable latency for write requests.

Abstract: Users intending to launch instances or otherwise access virtual resources in a multi-tenant environment can specify a launch configuration. For each type of instance or each type of user, at least one launch configuration is created that includes parameters and values to be used in instantiating an instance of that type, the values being optimized for the current environment and type of instance. Launch configurations can be optimized for different types of users, such as to account for security credentials and access levels. Such an approach enables users to launch instances by contacting the resource provider directly without need for a proxy, which can function as a choke point under heavy load. The use of an appropriate launch configuration can be enforced for any type of user at any level, such as at the sub-net level, by modifying a request that does not specify an appropriate launch configuration.

Abstract: The relative health of data storage drives may be determined based, at least in some aspects, on data access information and/or other drive operation information. In some examples, upon receiving the operation information from a computing device, a health level of a drive may be determined. The health level determination may be based at least in part on operating information received from a client entity. Additionally, a storage space allocation instruction or operation may be determined for execution. The allocation instruction or operation determined to be performed may be based at least in part on the determined health level.

Abstract: A system and method for predicting the likelihood of failure of the individual sectors of a magnetic storage disk based upon the monitoring of adjacent sector performance in responding to access requests. The prediction for a specific target sector's fidelity can be made through the gathering of sector performance data that occurs during normal read/write actions to the adjacent sectors, without a recent access request necessarily being made to the target sector. Scrubbing of the sectors can also be directed based upon the needed sector access data for target sector fidelity prediction.

Abstract: A storage controller is implemented for controlling a storage system. The storage controller may be implemented using a distributed computer system and may include components for servicing client data requests based on the characteristics of the distributed computer system, the client, or the data requests. The storage controller is scalable independently of the storage system it controls. All components of the storage controller, as well as the client, may be virtual or hardware-based instances of a distributed computer system.

Abstract: A storage controller is implemented for controlling a storage system. The storage controller may be implemented using a distributed computer system and may include components for servicing client data requests based on the characteristics of the distributed computer system, the client, or the data requests. The storage controller is scalable independently of the storage system it controls. All components of the storage controller, as well as the client, may be virtual or hardware-based instances of a distributed computer system.

Abstract: A storage controller is implemented for controlling a storage system. The storage controller may be implemented using a distributed computer system and may include components for servicing client data requests based on the characteristics of the distributed computer system, the client, or the data requests. The storage controller is scalable independently of the storage system it controls. All components of the storage controller, as well as the client, may be virtual or hardware-based instances of a distributed computer system.