Abstract: Systems and methods are described for enabling users to model security resources and user access keys as resources in a template language. The template can be used to create and update a stack of resources that will provide a network-accessible service. The security resources and access keys can be referred to in the template during both stack creation process and the stack update process. The security resources can include users, groups and policies. Additionally, users can refer to access keys in the template as dynamic parameters without any need to refer to the access keys in plaintext. The system securely stores access keys within the system and allows for templates to refer to them once defined. These key references can then be passed within a template to resources that need them as well as passing them on securely to resources like server instances through the use of the user-data field.

Abstract: Systems and methods are described for bootstrapping an application with metadata specified in a template. The template specifies a stack of resources that will be used to execute an application and also includes a set of metadata for customizing the resources and the application. When the system receives the template, it instantiates a compute node which will execute the application. The compute node may contain at least one initialization script for bootstrapping the application with the metadata contained in the template. This functionality allows users to bootstrap the application running on the compute node with data from within the template that was used to create the stack of resources for executing the application. In this manner, metadata, configuration files, package names and versions can be passed by the application owner to the remote compute node.

Abstract: At a time after receiving a request to cancel and rollback an update request for a computer system, one or more computer resources within a computer system invoke one or more computer system capabilities at least to cancel computer system operations to update the computer. When the computer system operations to update the computer system are cancelled, one or more computer resources within a computer system invoke one or more computer system capabilities at least to roll back the computer system to a previous good state.

Abstract: Techniques are described that enable a user to upgrade a stack of resources by providing a template that reflects the desired end state of the stack. Upon receiving a new template, the system automatically detects changes that should be performed and determines the order in which the changes should be performed. The system can also detect if the desired changes to the stack are a result of direct modifications; because parameters to the resources have changed; or the changes are indirectly caused by other dependency/attribute changing. Additionally, the system determines whether the changes require creating new resources or if the changes can be made to the resources live. In case of replacement of resources, the system will first create the new resource, move that new resource into the stack and remove the old resource(s). In case of failures, the system ensures that the stack rolls back to the initial state.

Abstract: Systems and methods are described for bootstrapping an application with metadata specified in a template. The template specifies a stack of resources that will be used to execute an application and also includes a set of metadata for customizing the resources and the application. When the system receives the template, it instantiates a compute node which will execute the application. The compute node may contain at least one initialization script for bootstrapping the application with the metadata contained in the template. This functionality allows users to bootstrap the application running on the compute node with data from within the template that was used to create the stack of resources for executing the application. In this manner, metadata, configuration files, package names and versions can be passed by the application owner to the remote compute node.

Abstract: Technologies are disclosed herein for providing an asynchronous fleet configuration service for deploying and updating a fleet of network resources. The asynchronous fleet configuration service exposes an asynchronous application programming interface (API) that allows for individual resources to indicate an initialization status. Accordingly, the asynchronous fleet configuration service can asynchronously monitor the status of individual resources being deployed or updated, while performing other duties related to the fleet of network resources.

Abstract: Systems and methods are described for bootstrapping an application with metadata specified in a template. The template specifies a stack of resources that will be used to execute an application and also includes a set of metadata for customizing the resources and the application. When the system receives the template, it instantiates a compute node which will execute the application. The compute node may contain at least one initialization script for bootstrapping the application with the metadata contained in the template. This functionality allows users to bootstrap the application running on the compute node with data from within the template that was used to create the stack of resources for executing the application. In this manner, metadata, configuration files, package names and versions can be passed by the application owner to the remote compute node.

Abstract: Techniques for executing commands associated with system stacks using parallel workflows are described herein. A dependency representation based at least in part on a stack description is created. The stack description describes stack resource instance and dependencies between those resource instances. The dependency representation is then analyzed to determine sub-workflows each of which may be executed in parallel. The sub-workflows may be altered based on one or more runtime interdependencies and the stack command may be executed by performing the sub-workflows in a determined order.

Abstract: Techniques are described that enable a user to upgrade a stack of resources by providing a template that reflects the desired end state of the stack. Upon receiving a new template, the system automatically detects changes that should be performed and determines the order in which the changes should be performed. The system can also detect if the desired changes to the stack are a result of direct modifications; because parameters to the resources have changed; or the changes are indirectly caused by other dependency/attribute changing. Additionally, the system determines whether the changes require creating new resources or if the changes can be made to the resources live. In case of replacement of resources, the system will first create the new resource, move that new resource into the stack and remove the old resource(s). In case of failures, the system ensures that the stack rolls back to the initial state.

Abstract: A resource stack managed by a resource stack provider is created based on a resource stack template that integrates a custom resource from a second provider into the resource stack using a notification system with the second provider. For example, a customer may create a template that defines a resource stack that comprises resources available from the resource stack provider and one or more custom resources provided by a second provider. When a resource stack is created, resources available from the resource stack provider may be provisioned. Custom resources may be initialized by notifying the provider of the custom resource of the requested integration of the custom resource with the resource stack and requested configuration details. The custom resource provider may respond with an indication of successful integration when the custom resource has been successfully initialized. After initializing the resources, the resource stack may be enabled for use.

Abstract: Techniques are described that enable a user to upgrade a stack of resources by providing a template that reflects the desired end state of the stack. Upon receiving a new template, the system automatically detects changes that should be performed and determines the order in which the changes should be performed. The system can also detect if the desired changes to the stack are a result of direct modifications; because parameters to the resources have changed; or the changes are indirectly caused by other dependency/attribute changing. Additionally, the system determines whether the changes require creating new resources or if the changes can be made to the resources live. In case of replacement of resources, the system will first create the new resource, move that new resource into the stack and remove the old resource(s). In case of failures, the system ensures that the stack rolls back to the initial state.

Abstract: Techniques for cancel and rollback of update stack requests are disclosed herein. At a time after receiving a request to cancel and rollback an update request for a computer system, one or more computer resources within a computer system invoke one or more computer system capabilities at least to cancel computer system operations to update the computer. When the computer system operations to update the computer system are cancelled, one or more computer resources within a computer system invoke one or more computer system capabilities at least to roll back the computer system to a previous good state.

Abstract: At a time after receiving a request to cancel and rollback an update request for a computer system, one or more computer resources within a computer system invoke one or more computer system capabilities at least to cancel computer system operations to update the computer. When the computer system operations to update the computer system are cancelled, one or more computer resources within a computer system invoke one or more computer system capabilities at least to roll back the computer system to a previous good state.

Abstract: A resource stack managed by a resource stack provider is created based on a resource stack template that integrates a custom resource from a second provider into the resource stack using a notification system with the second provider. For example, a customer may create a template that defines a resource stack that comprises resources available from the resource stack provider and one or more custom resources provided by a second provider. When a resource stack is created, resources available from the resource stack provider may be provisioned. Custom resources may be initialized by notifying the provider of the custom resource of the requested integration of the custom resource with the resource stack and requested configuration details. The custom resource provider may respond with an indication of successful integration when the custom resource has been successfully initialized. After initializing the resources, the resource stack may be enabled for use.

Abstract: A resource stack managed by a resource stack provider is created based on a resource stack template that integrates a custom resource from a second provider into the resource stack using a notification system with the second provider. For example, a customer may create a template that defines a resource stack that comprises resources available from the resource stack provider and one or more custom resources provided by a second provider. When a resource stack is created, resources available from the resource stack provider may be provisioned. Custom resources may be initialized by notifying the provider of the custom resource of the requested integration of the custom resource with the resource stack and requested configuration details. The custom resource provider may respond with an indication of successful integration when the custom resource has been successfully initialized. After initializing the resources, the resource stack may be enabled for use.

Abstract: Systems and methods are described for enabling users to model security resources and user access keys as resources in a template language. The template can be used to create and update a stack of resources that will provide a network-accessible service. The security resources and access keys can be referred to in the template during both stack creation process and the stack update process. The security resources can include users, groups and policies. Additionally, users can refer to access keys in the template as dynamic parameters without any need to refer to the access keys in plaintext. The system securely stores access keys within the system and allows for templates to refer to them once defined. These key references can then be passed within a template to resources that need them as well as passing them on securely to resources like server instances through the use of the user-data field.

Abstract: Systems and methods are described for enabling users to model security resources and user access keys as resources in a template language. The template can be used to create and update a stack of resources that will provide a network-accessible service. The security resources and access keys can be referred to in the template during both stack creation process and the stack update process. The security resources can include users, groups and policies. Additionally, users can refer to access keys in the template as dynamic parameters without any need to refer to the access keys in plaintext. The system securely stores access keys within the system and allows for templates to refer to them once defined. These key references can then be passed within a template to resources that need them as well as passing them on securely to resources like server instances through the use of the user-data field.

Abstract: Techniques for cancel and rollback of update stack requests are disclosed herein. At a time after receiving a request to cancel and rollback an update request for a computer system, one or more computer resources within a computer system invoke one or more computer system capabilities at least to cancel computer system operations to update the computer. When the computer system operations to update the computer system are cancelled, one or more computer resources within a computer system invoke one or more computer system capabilities at least to roll back the computer system to a previous good state.

Abstract: At a time after receiving a request to cancel and rollback an update request for a computer system, one or more computer resources within a computer system invoke one or more computer system capabilities at least to cancel computer system operations to update the computer. When the computer system operations to update the computer system are cancelled, one or more computer resources within a computer system invoke one or more computer system capabilities at least to roll back the computer system to a previous good state.

Abstract: A resource stack managed by a resource stack provider is created based on a resource stack template that integrates a custom resource from a second provider into the resource stack using a notification system with the second provider. For example, a customer may create a template that defines a resource stack that comprises resources available from the resource stack provider and one or more custom resources provided by a second provider. When a resource stack is created, resources available from the resource stack provider may be provisioned. Custom resources may be initialized by notifying the provider of the custom resource of the requested integration of the custom resource with the resource stack and requested configuration details. The custom resource provider may respond with an indication of successful integration when the custom resource has been successfully initialized. After initializing the resources, the resource stack may be enabled for use.