Abstract: Techniques are described for providing a highly available data ingestion system for ingesting machine data sent from remote data sources across potentially unreliable networks. To provide for highly available delivery of such data, a data intake and query system provides users with redundant sets of ingestion endpoints to which messages sent from users' computing environments can be delivered to the data intake and query system. Users' data sources, or data forwarding components configured to obtain and send data from one or more data sources, are then configured to encapsulate obtained machine data into discrete messages and to send copies of each message to two or more of the ingestion endpoints provisioned for a user. The ingestion endpoints receiving the messages implement a deduplication technique and provide only one copy of each message to a subsequent processing component (e.g., to an indexing subsystem for event generation, event indexing, etc.).

Abstract: A method and apparatus for task scheduling, execution and monitoring are provided. In the method and apparatus, a task package specifying at least one of a task, a task trigger or an execution environment is received. An execution environment is instantiated and the task is sent to the execution environment for execution.

Abstract: A customer may use a disaster recovery service to generate a disaster recovery scenario in order to make certain resources available to the customer in the event of a data region failure. The customer may specify a recovery point objective, a recovery time objective and a recovery data region for the scenario. Accordingly, the disaster recovery service may coordinate with one or more other services provided by the computing resource service provider to reproduce the customer resources and other resources necessary to support the customer resources. These reproduced resources may be transferred to the recovery data region based at least in part on the parameters specified by the customer. In the event of a data region failure, the disaster recovery service may update the domain name system to resolve any customer requests for the customer resources to the recovery data region.

Abstract: A data storage service receives commands configured according to a communication protocol, such as a small computer system interface protocol. The commands may be replications of commands sent to a block-level data storage system, such as a storage area network. Data to be written by execution of the commands is persisted using an object-based data storage system. When read commands are received, data blocks can be extracted from the data objects in which they are stored.

Abstract: A method and apparatus for task scheduling, execution and monitoring are provided. In the method and apparatus, a task package specifying at least one of a task, a task trigger or an execution environment is received. An execution environment is instantiated and the task is sent to the execution environment for execution.

Abstract: A method and apparatus for task scheduling, execution and monitoring are provided. In the method and apparatus, a task package specifying at least one of a task, a task trigger or an execution environment is received. An execution environment is instantiated and the task is sent to the execution environment for execution.

Abstract: Organizations are constantly looking for faster and less expensive computer systems to manage businesses; however, the current standard in virtualization techniques includes using virtual machines, which require a long period of time to be instantiated before handling requests and are resource intensive. Using Domain Name System (DNS) queries to a DNS server as an indicator to initiate a virtual resource, such as containers, enables the system to instantiate the container prior to an end user transmitting their first request for a resource stored in that container. Containers can be initialized upon indication of a request, terminated at the end of the request process and initialized again for a next request as they can be activated at very fast speeds as needed. Additionally, using DNS queries as indicators to warm a cache of a network component enables the system components to be imminently used, to be pre-loaded with requested resources.

Abstract: A customer may use a disaster recovery service to generate a disaster recovery scenario in order to make certain resources available to the customer in the event of a data region failure. The customer may specify a recovery point objective, a recovery time objective and a recovery data region for the scenario. Accordingly, the disaster recovery service may coordinate with one or more other services provided by the computing resource service provider to reproduce the customer resources and other resources necessary to support the customer resources. These reproduced resources may be transferred to the recovery data region based at least in part on the parameters specified by the customer. In the event of a data region failure, the disaster recovery service may update the domain name system to resolve any customer requests for the customer resources to the recovery data region.

Abstract: An object-based data storage system receives a request to create a logical data container subject to a condition that data objects are to be unmodifiable until after a specified amount of time has transpired. During the amount of time, the object-based data storage system may deny any requests to modify the data objects stored in the logical data container while allowing read-only access to the data objects. After the amount of time has transpired, the object-based data storage system may be configured to allow a customer to modify or delete any data objects stored within the logical data container. Alternatively, the object-based data storage system may be configured to delete the data objects automatically after the amount of time has transpired for the data objects.

Abstract: A customer may use a disaster recovery service to generate a disaster recovery scenario in order to make certain resources available to the customer in the event of a data region failure. The customer may specify a recovery point objective, a recovery time objective and a recovery data region for the scenario. Accordingly, the disaster recovery service may coordinate with one or more other services provided by the computing resource service provider to reproduce the customer resources and other resources necessary to support the customer resources. These reproduced resources may be transferred to the recovery data region based at least in part on the parameters specified by the customer. In the event of a data region failure, the disaster recovery service may update the domain name system to resolve any customer requests for the customer resources to the recovery data region.

Abstract: A customer may use a disaster recovery service to generate a disaster recovery scenario in order to make certain resources available to the customer in the event of a data region failure. The customer may specify a recovery point objective, a recovery time objective and a recovery data region for the scenario. Accordingly, the disaster recovery service may coordinate with one or more other services provided by the computing resource service provider to reproduce the customer resources and other resources necessary to support the customer resources. These reproduced resources may be transferred to the recovery data region based at least in part on the parameters specified by the customer. In the event of a data region failure, the disaster recovery service may update the domain name system to resolve any customer requests for the customer resources to the recovery data region.

Abstract: A customer may use a disaster recovery service to generate a disaster recovery scenario in order to make certain resources available to the customer in the event of a data region failure. The customer may specify a recovery point objective, a recovery time objective and a recovery data region for the scenario. Accordingly, the disaster recovery service may coordinate with one or more other services provided by the computing resource service provider to reproduce the customer resources and other resources necessary to support the customer resources. These reproduced resources may be transferred to the recovery data region based at least in part on the parameters specified by the customer. In the event of a data region failure, the disaster recovery service may update the domain name system to resolve any customer requests for the customer resources to the recovery data region.

Abstract: Organizations are constantly looking for faster and less expensive computer systems to manage businesses; however, the current standard in virtualization techniques includes using virtual machines, which require a long period of time to be instantiated before handling requests and are resource intensive. Using Domain Name System (DNS) queries to a DNS server as an indicator to initiate a virtual resource, such as containers, enables the system to instantiate the container prior to an end user transmitting their first request for a resource stored in that container. Containers can be initialized upon indication of a request, terminated at the end of the request process and initialized again for a next request as they can be activated at very fast speeds as needed. Additionally, using DNS queries as indicators to warm a cache of a network component enables the system components to be imminently used, to be pre-loaded with requested resources.