Abstract: An object-based data storage service receives a request to store a data object in association with a smart data storage tier. Based at least in part on characteristics of the data object, the object-based data storage service identifies and stores the data object in a first location corresponding to a first data storage tier. The object-based data storage service monitors access to the data object to identify a second set of characteristics of the data object. This second set of characteristics is used to determine that the data object is to be transitioned to a second data storage tier. The object-based data storage service, based at least in part on this determination, stores the data object in a second location corresponding to the second data storage tier.

Abstract: An object storage system includes mass storage devices that implement general storage for objects stored in the object storage system and additionally includes other storage devices, such as solid-state drives, that provide higher performance storage access. The object storage system implements a common access interface for accessing both accelerated access objects (who are eligible to have cached copies stored on the higher performance storage devices) and non-accelerated access objects stored in the general storage. The cache is fully managed by the service and no changes are required for client applications to receive accelerated access to objects that are classified as accelerated access objects per a customer configurable acceleration policy for the object or for a bucket in which the object is stored.

Abstract: An object storage system includes mass storage devices that implement general storage for objects stored in the object storage system and additionally includes other storage devices, such as solid-state drives, that provide higher performance storage access. The object storage system implements a common access interface for accessing both accelerated access objects (who are eligible to have cached copies stored on the higher performance storage devices) and non-accelerated access objects stored in the general storage. The cache is fully managed by the service and no changes are required for client applications to receive accelerated access to objects that are classified as accelerated access objects per a customer configurable acceleration policy for the object or for a bucket in which the object is stored.

Abstract: An object-based data storage service receives a request to store a data object in association with a smart data storage tier. Based at least in part on characteristics of the data object, the object-based data storage service identifies and stores the data object in a first location corresponding to a first data storage tier. The object-based data storage service monitors access to the data object to identify a second set of characteristics of the data object. This second set of characteristics is used to determine that the data object is to be transitioned to a second data storage tier. The object-based data storage service, based at least in part on this determination, stores the data object in a second location corresponding to the second data storage tier.

Abstract: An object-based data storage service receives a request to store a data object in association with a smart data storage tier. Based at least in part on characteristics of the data object, the object-based data storage service identifies and stores the data object in a first location corresponding to a first data storage tier. The object-based data storage service monitors access to the data object to identify a second set of characteristics of the data object. This second set of characteristics is used to determine that the data object is to be transitioned to a second data storage tier. The object-based data storage service, based at least in part on this determination, stores the data object in a second location corresponding to the second data storage tier.

Abstract: Dynamic management of data traffic workflows is performed. An event to perform a data traffic workflow at a remote performance location may be received. Computing resources to perform the data traffic workflow may be identified. Operations to perform the data traffic workflow may be dynamically directed by the identified computing resources to adaptively balance performance of the operations with operations for other data traffic workflows in order to meet respective performance requirements of the data traffic workflows.

Abstract: An object-based data storage service receives a request to store a data object in association with a smart data storage tier. Based at least in part on characteristics of the data object, the object-based data storage service identifies and stores the data object in a first location corresponding to a first data storage tier. The object-based data storage service monitors access to the data object to identify a second set of characteristics of the data object. This second set of characteristics is used to determine that the data object is to be transitioned to a second data storage tier. The object-based data storage service, based at least in part on this determination, stores the data object in a second location corresponding to the second data storage tier.

Abstract: An object-based data storage service receives a request to store a data object in association with a smart data storage tier. Based at least in part on characteristics of the data object, the object-based data storage service identifies and stores the data object in a first location corresponding to a first data storage tier. The object-based data storage service monitors access to the data object to identify a second set of characteristics of the data object. This second set of characteristics is used to determine that the data object is to be transitioned to a second data storage tier. The object-based data storage service, based at least in part on this determination, stores the data object in a second location corresponding to the second data storage tier.

Abstract: The performance of asynchronous tasks may be dynamically configured. An evaluation of pending tasks that includes updates for new tasks and completed tasks being removed is performed. A target capacity for the data traffic workflow is determined from the evaluation of pending tasks in order to satisfy a performance requirement for the data traffic workflow. Modifications to a performance configuration for the data traffic workflow are then made based on a comparison with the target capacity.

Abstract: A data transport service of a provider network provide isolated and flexible network data transmission between different computing infrastructure collections of the provider network (e.g., between different geographical regions) for different users. The data transport service may receive a request from a user for assignment of a channel. The request specifies a desired capacity of the channel to transmit data from a computing infrastructure collection to another a computing infrastructure collection. Based on the requested capacity for the channel, the data transport service may reserve, for the channel, network resource capacity to transmit the data between the infrastructures and reserve, for the channel, compute instance capacity to ingest the data and to send the data between the infrastructures using the reserved network resource capacity. The reserved network resource capacity and reserved compute instance capacity are dedicated to the channel and are unavailable for use by other channels.

Abstract: Techniques for maintaining versioning of data objects as a result of policy-based changes to the data objects are described herein. Metadata associated with a data object is updated as a result of an operation that is specified in a data policy associated with the data object. The metadata associated with the data object is updated based on a version key that is associated with the data object that is an identifier that identifies the data storage object in a plurality of data storage classes.

Abstract: An object-based data storage service receives a request to store a data object in association with a smart data storage tier. Based at least in part on characteristics of the data object, the object-based data storage service identifies and stores the data object in a first location corresponding to a first data storage tier. The object-based data storage service monitors access to the data object to identify a second set of characteristics of the data object. This second set of characteristics is used to determine that the data object is to be transitioned to a second data storage tier. The object-based data storage service, based at least in part on this determination, stores the data object in a second location corresponding to the second data storage tier.

Abstract: An object-based data storage service receives a request to store a data object in association with a smart data storage tier. Based at least in part on characteristics of the data object, the object-based data storage service identifies and stores the data object in a first location corresponding to a first data storage tier. The object-based data storage service monitors access to the data object to identify a second set of characteristics of the data object. This second set of characteristics is used to determine that the data object is to be transitioned to a second data storage tier. The object-based data storage service, based at least in part on this determination, stores the data object in a second location corresponding to the second data storage tier.

Abstract: A version of a data object is updated as a result of a version changing operation and version metadata associated with the data object is updated based on a version key that is associated with the data object where the version metadata maintains a history of the version changing operations performed on the data object.

Abstract: Systems and methods for processing requests associated with network resources and/or virtualization services are provided. A request associated with one or more network resources may be received, and a set of one or more tags associated with the request may be identified. A representative value for the set of one or more tags may then be determined utilizing, for example, a hashing operation or a compression function. The representative value may be associated with a request prior to the request being processed by at least one network server. Subsequently, the set of one or more tags may reconstructed based at least in part upon the representative value in order to facilitate the generation of one or more reports, such as billing reports or resource usage reports.

Abstract: Systems and methods for processing requests associated with network resources and/or virtualization services are provided. A request associated with one or more network resources may be received, and a set of one or more tags associated with the request may be identified. A representative value for the set of one or more tags may then be determined utilizing, for example, a hashing operation or a compression function. The representative value may be associated with a request prior to the request being processed by at least one network server. Subsequently, the set of one or more tags may reconstructed based at least in part upon the representative value in order to facilitate the generation of one or more reports, such as billing reports or resource usage reports.

Abstract: The present invention encompasses a method in a client-server communication system wherein the method comprises one or more stages for content transformation, which renders data into presentation format. The method comprises at least stage for content transformation that is based on device used by the client.

Abstract: An Interface Markup Language (“IML”) file specifies abstract server interface definitions called “operations” that return abstract content descriptions called “entities”. Each entity specifies a set of operations that the entity can invoke. The combined set of entities and operations together define an abstract flow diagram of an application. A computer readable medium has instructions stored thereon which, when executed by a processor, cause the processor to perform a sequence of steps in order to make application code that is based on a flow diagram of an application. The steps include making an IML file that includes an operation list section delimited by an operation list marker and an entity list section delimited by an entity list marker. The operation list section specifies a series of operations supported by an application server. The entity list section describes a set of entities which constitute an interface to an application running on the application server.