Abstract: A service management system prepares computing resources for use before a client requests the resource. For example, a service management system of a provider may restore an operating system image to a volume. The service management may then assign a processing resource to the volume to form a virtual machine. The service management system may cause the processing resource to finish preparation of the operating system on the volume. The service management system may disconnect the resulting staged volume from the processing resource. The staged volume may remain active in the low-latency data store and be added to a list of available staged volumes having the operating system. When a client requests a virtual machine having an operating system, the service management system may determine that the client receives the staged volume as part of the virtual machine to avoid the start-up costs of preparing a volume.

Abstract: A host computing device can include a host domain that includes an agent for configuring the operation and/or functionality of virtual machine instances and/or operating systems associated with the instances, which may be heterogeneous (i.e., running different operating systems than each other). One or more data volumes associated with the host machine can include an image of an operating system. In an embodiment the agent can access the image of the operating system and configure operating system settings, add data, and/or remove data.

Abstract: A host computing device can include a host domain that includes an agent for configuring the operation and/or functionality of virtual machine instances and/or operating systems associated with the instances, which may be heterogeneous (i.e., running different operating systems than each other). One or more data volumes associated with the host machine can include an image of an operating system. In an embodiment the agent can access the image of the operating system and configure operating system settings, add data, and/or remove data.

Abstract: A host computing device can include a host domain that includes an agent for configuring the operation and/or functionality of virtual machine instances and/or operating systems associated with the instances, which may be heterogeneous (i.e., running different operating systems than each other). One or more data volumes associated with the host machine can include an image of an operating system. In an embodiment the agent can access the image of the operating system and configure operating system settings, add data, and/or remove data.

Abstract: A distributed lock manager (DLM) may be implemented in a distributed computing system that provides virtualized computing resources and/or virtual computing services to clients. Locks may be created and managed by the DLM in response to requests from clients to do so. The components of the DLM may communicate with each other over a network other than one over which client application components communicate with each other or access the shared resources protected by the locks. For example, DLM components may communicate over a control plane network of a cloud computing environment and application components may communicate over a data plane network of the cloud computing environment. The DLM may expose an API to clients, allowing them to make local calls to a DLM component on the same node to perform various lock management operations. The meanings of the lock values may be established by their use in client applications.

Abstract: A system and method for remotely interacting with a virtualized machine instance (VMI) through a trigger mechanism resident at the VMI. When the VMI receives a request via the trigger mechanism, the VMI responds to the request, such as by obtaining a program and executing the program locally at the VMI.

Abstract: A system and method for remotely interacting with a virtualized machine instance (VMI) through a trigger mechanism resident at the VMI. When the VMI receives a request via the trigger mechanism, the VMI responds to the request, such as by obtaining a program and executing the program locally at the VMI.

Abstract: A proxy operating inside of a virtual machine that is responsible for receiving user-specified configuration information, such as credentials, and updating the configuration of the virtual machine with the user-specified values at the time of assigning the virtual machine to a user. Once the proxy updates the configuration of the virtual machine, the virtual machine is assigned the user that provided the user configuration information and the proxy can deactivate or uninstall itself from the virtual machine, such as by deleting all files, registry entries and other traces of execution.

Abstract: A distributed lock manager (DLM) may be implemented in a distributed computing system that provides virtualized computing resources and/or virtual computing services to clients. Locks may be created and managed by the DLM in response to requests from clients to do so. The components of the DLM may communicate with each other over a network other than one over which client application components communicate with each other or access the shared resources protected by the locks. For example, DLM components may communicate over a control plane network of a cloud computing environment and application components may communicate over a data plane network of the cloud computing environment. The DLM may expose an API to clients, allowing them to make local calls to a DLM component on the same node to perform various lock management operations. The meanings of the lock values may be established by their use in client applications.