Abstract: Aspects described herein relate to securely performing cross-boundary backup operations. A service of a computing resource service provider may enable backup operations between a source account and a destination account of an organization based at least in part on a security policy allowing such operations.

Abstract: Systems and methods are described herein for routing data by transferring a physical storage device for at least part of a route between source and destination locations. In one example, a computing resource service provider, may receive a request to transfer data from a customer center to a data center. The service provider may determine a route, which includes one or more of a physical path or a network path, for the data loaded onto a physical storage device to reach the data center from the customer center. Determining the route may include associating respective cost values to individual physical and network paths between physical stations between the customer and end data centers, and selecting one or more of the paths to reduce a total cost of the route. Route information may then be associated with the physical storage device based on the route.

Abstract: A client request, formatted in accordance with a file system interface, is received at an access subsystem of a distributed multi-tenant storage service. After the request is authenticated at the access subsystem, an atomic metadata operation comprising a group of file system metadata modifications is initiated, including a first metadata modification at a first node of a metadata subsystem of the storage service and a second metadata modification at a second node of the metadata subsystem. A plurality of replicas of at least one data modification corresponding to the request are saved at respective storage nodes of the service.

Abstract: A low latency metadata subsystem for file systems in low latency (LL) mode in a distributed file storage service (DFSS). An LL server (LLS) may receive metadata requests from an access node of the DFSS. For read operations, the LLS may check a local cache of metadata and, for cache hits, retrieve the metadata from the cache. For cache misses, the metadata may be fetched from the storage subsystem of the DFSS and cached. For write operations, the LLS may write entries into a journal for the file system and notify the access node after the journal entries are committed to the journal; the journal entries are asynchronously committed in the storage subsystem. The access node may communicate with the storage subsystem to perform data reads and writes for the LL file system.

Abstract: A low latency metadata subsystem for file systems in low latency (LL) mode in a distributed file storage service (DFSS). An LL server (LLS) may receive metadata requests from an access node of the DFSS. For read operations, the LLS may check a local cache of metadata and, for cache hits, retrieve the metadata from the cache. For cache misses, the metadata may be fetched from the storage subsystem of the DFSS and cached. For write operations, the LLS may write entries into a journal for the file system and notify the access node after the journal entries are committed to the journal; the journal entries are asynchronously committed in the storage subsystem. The access node may communicate with the storage subsystem to perform data reads and writes for the LL file system.

Abstract: An I/O request directed to a portion of a storage object managed at a distributed storage service is received. A congestion control parameter value to be used to schedule a storage operation corresponding to the I/O request is determined. The congestion control parameter is based at least in part on an offset within the storage object to which the I/O request is directed. The storage operation is scheduled in accordance with the congestion control parameter at a selected physical storage device to which the portion of the storage object is mapped.

Abstract: An I/O request directed to a portion of a storage object managed at a distributed storage service is received. A congestion control parameter value to be used to schedule a storage operation corresponding to the I/O request is determined. The congestion control parameter is based at least in part on an offset within the storage object to which the I/O request is directed. The storage operation is scheduled in accordance with the congestion control parameter at a selected physical storage device to which the portion of the storage object is mapped.

Abstract: An I/O request directed to a portion of a storage object managed at a distributed storage service is received. A congestion control parameter value to be used to schedule a storage operation corresponding to the I/O request is determined. The congestion control parameter is based at least in part on an offset within the storage object to which the I/O request is directed. The storage operation is scheduled in accordance with the congestion control parameter at a selected physical storage device to which the portion of the storage object is mapped.

Abstract: A client request, formatted in accordance with a file system interface, is received at an access subsystem of a distributed multi-tenant storage service. After the request is authenticated at the access subsystem, an atomic metadata operation comprising a group of file system metadata modifications is initiated, including a first metadata modification at a first node of a metadata subsystem of the storage service and a second metadata modification at a second node of the metadata subsystem. A plurality of replicas of at least one data modification corresponding to the request are saved at respective storage nodes of the service.