Abstract: Techniques for managing latency of communications between compute instances and mobile devices are described. A message including an indication of a mobility event associated with a mobile device of a communications service provider network is received. The mobility event indicates a change in a connection point of the mobile device to the communications service provider network from a from a first access point to a second access point. A communications delay of at least a portion of a network path between the mobile device and a compute instance via the second access point is determined to not satisfy a latency constraint. A second provider substrate extension of the cloud provider network that satisfies the latency constraint for communications with the mobile device via the second access point is identified, and a message is sent to the second provider substrate extension to cause the launch of another compute instance.

Abstract: A virtual computer system service receives a request from a customer to provision a dedicated server for the exclusive use of the customer. The dedicated server may be used to launch one or more virtual machine instances. The virtual computer system service subsequently selects, from a pool of available servers, a server that can be dedicated to the customer and that does not have capacity allocated to any other customer. The virtual computer system service may update a database to specify, in an entry corresponding to the selected server, that the server has been dedicated for the exclusive use of the customer. Once the database has been updated, the virtual computer system service will enable the customer to launch a virtual machine instance using the dedicated server.

Abstract: Techniques are described for enabling users of a service provider network to create and configure “application profiles” that include parameters related to execution of user workloads at provider substrate extensions. Once an application profile is created, users can request the deployment of user workloads to provider substrate extensions by requesting instance launches based on a defined application profile. The service provider network can then automate the launch and placement of the user's workload at one or more provider substrate extensions using edge-optimized compute instances (e.g., compute instances tailored for execution within provider substrate extension environments).

Abstract: Techniques are described for enabling users of a service provider network to create and configure “application profiles” that include parameters related to execution of user workloads at provider substrate extensions. Once an application profile is created, users can request the deployment of user workloads to provider substrate extensions by requesting instance launches based on a defined application profile. The service provider network can then automate the launch and placement of the user's workload at one or more provider substrate extensions using edge-optimized compute instances (e.g., compute instances tailored for execution within provider substrate extension environments).

Abstract: Techniques for utilizing dual-stack network addressing for compute instances hosted in an edge location of a cloud provider network along with communications service provider (CSP) network addresses are described. A first network address is assigned to the compute instance from a pool of network addresses of the cloud provider network, and a second network address is associated with the compute instance that is provided by the CSP network. A gateway of the edge location is updated to direct packets addressed to the second network address to the compute instance via use of the first network address.

Abstract: Techniques for dynamic resource movement in heterogeneous computing environments including provider substrate extensions are described. A dynamic resource movement service of a provider network monitor conditions of heterogeneous computing environments, including provider substrate extensions of the cloud provider network, to evaluate customer-provided movement policy conditions governing when to move customer application resources from these environments, where to move the resource to, and/or how to move the customer application resources. The customer-provided movement policy conditions may be based on a variety of factors, such as a latency between end-users of the customer application and the application itself.

Abstract: Techniques are described for a cloud provider to provide a managed experience related to the use of virtual networks and subnets to logically group user computing resources deployed at provider substrate extensions. A cloud provider enables users to create virtual network templates used when deploying computing resources at provider substrate extensions, where such virtual network templates may include various networking, security, and other configurations to be applied to network traffic and other activity of resources deployed within an associated virtual network. Once a virtual network template is defined, a user can use the template as the basis to launch resources into the virtual network and, by extension, into provider substrate extensions associated with the virtual network. Upon receiving such a request, the provider network can manage the creation and configuration of underlying subnets, route tables, and other resource, as needed, at each of the relevant provider substrate extensions.

Abstract: Techniques are described for enabling users of a service provider network to create and configure “application profiles” that include parameters related to execution of user workloads at provider substrate extensions. Once an application profile is created, users can request the deployment of user workloads to provider substrate extensions by requesting instance launches based on a defined application profile. The service provider network can then automate the launch and placement of the user's workload at one or more provider substrate extensions using edge-optimized compute instances (e.g., compute instances tailored for execution within provider substrate extension environments).

Abstract: Techniques for automated failover of remote control planes are described. A method of automated failover of remote control planes include determining failover event associated with a first control plane has occurred, the first control plane associated with a first area of a provider network, identifying a second control plane associated with a second area of the provider network, and failing over the first area of the provider network from the first control plane to the second control plane, wherein the child area updates one or more references to endpoints of the first control plane to be references to endpoints of the second control plane.

Abstract: Techniques for managing latency of communications between compute instances and mobile devices are described. A message including an indication of a mobility event associated with a mobile device of a communications service provider network is received. The mobility event indicates a change in a connection point of the mobile device to the communications service provider network from a from a first access point to a second access point. A communications delay of at least a portion of a network path between the mobile device and a compute instance via the second access point is determined to not satisfy a latency constraint. A second provider substrate extension of the cloud provider network that satisfies the latency constraint for communications with the mobile device via the second access point is identified, and a message is sent to the second provider substrate extension to cause the launch of another compute instance.

Abstract: Techniques for capacity bursting using a remote control plane are described. A method of capacity bursting using a remote control plane includes determining that a first control plane associated with a first area of a provider network has insufficient capacity to manage a plurality of resources in the first area, sending a request for a second control plane in a second area of the provider network to manage at least a first portion of the plurality of resources in the first area, the second control plane identified based at least on a backup hierarchy, and updating management of at least the first portion of the resources in the first area from the first control plane to the second control plane, wherein one or more references to endpoints of the first control plane are updated to be references to endpoints of the second control plane for at least the first portion of the resources managed by the second control plane.

Abstract: Techniques for dynamic resource movement in heterogeneous computing environments including provider substrate extensions are described. A dynamic resource movement service of a provider network monitor conditions of heterogeneous computing environments, including provider substrate extensions of the cloud provider network, to evaluate customer-provided movement policy conditions governing when to move customer application resources from these environments, where to move the resource to, and/or how to move the customer application resources. The customer-provided movement policy conditions may be based on a variety of factors, such as a latency between end-users of the customer application and the application itself.

Abstract: A virtual computer system service receives a request from a customer to provision a dedicated server for the exclusive use of the customer. The dedicated server may be used to launch one or more virtual machine instances. The virtual computer system service subsequently selects, from a pool of available servers, a server that can be dedicated to the customer and that does not have capacity allocated to any other customer. The virtual computer system service may update a database to specify, in an entry corresponding to the selected server, that the server has been dedicated for the exclusive use of the customer. Once the database has been updated, the virtual computer system service will enable the customer to launch a virtual machine instance using the dedicated server.

Abstract: Techniques for dynamic resource movement in heterogeneous computing environments including provider substrate extensions are described. A dynamic resource movement service of a provider network monitor conditions of heterogeneous computing environments, including provider substrate extensions of the cloud provider network, to evaluate customer-provided movement policy conditions governing when to move customer application resources from these environments, where to move the resource to, and/or how to move the customer application resources. The customer-provided movement policy conditions may be based on a variety of factors, such as a latency between end-users of the customer application and the application itself.

Abstract: Techniques for dynamic resource movement in heterogeneous computing environments including provider substrate extensions are described. A dynamic resource movement service of a provider network monitor conditions of heterogeneous computing environments, including provider substrate extensions of the cloud provider network, to evaluate customer-provided movement policy conditions governing when to move customer application resources from these environments, where to move the resource to, and/or how to move the customer application resources. The customer-provided movement policy conditions may be based on a variety of factors, such as a latency between end-users of the customer application and the application itself.

Abstract: Techniques for managing latency of communications between compute instances and mobile devices are described. A message including an indication of a mobility event associated with a mobile device of a communications service provider network is received. The mobility event indicates a change in a connection point of the mobile device to the communications service provider network from a from a first access point to a second access point. A communications delay of at least a portion of a network path between the mobile device and a compute instance via the second access point is determined to not satisfy a latency constraint. A second provider substrate extension of the cloud provider network that satisfies the latency constraint for communications with the mobile device via the second access point is identified, and a message is sent to the second provider substrate extension to cause the launch of another compute instance.

Abstract: Techniques for dynamic resource movement in heterogeneous computing environments including provider substrate extensions are described. A dynamic resource movement service of a provider network monitor conditions of heterogeneous computing environments, including provider substrate extensions of the cloud provider network, to evaluate customer-provided movement policy conditions governing when to move customer application resources from these environments, where to move the resource to, and/or how to move the customer application resources. The customer-provided movement policy conditions may be based on a variety of factors, such as a latency between end-users of the customer application and the application itself.

Abstract: Techniques are described for enabling users of a service provider network to create and configure “application profiles” that include parameters related to execution of user workloads at provider substrate extensions. Once an application profile is created, users can request the deployment of user workloads to provider substrate extensions by requesting instance launches based on a defined application profile. The service provider network can then automate the launch and placement of the user's workload at one or more provider substrate extensions using edge-optimized compute instances (e.g., compute instances tailored for execution within provider substrate extension environments).

Abstract: A virtual computer system service receives a request from a customer to provision a dedicated server for the exclusive use of the customer. The dedicated server may be used to launch one or more virtual machine instances. The virtual computer system service subsequently selects, from a pool of available servers, a server that can be dedicated to the customer and that does not have capacity allocated to any other customer. The virtual computer system service may update a database to specify, in an entry corresponding to the selected server, that the server has been dedicated for the exclusive use of the customer. Once the database has been updated, the virtual computer system service will enable the customer to launch a virtual machine instance using the dedicated server.

Abstract: Techniques for launching compute instances on cloud provider network substrate extensions deployed within communications service provider networks are described. A service of a cloud provider network receives a request to launch a compute instance from a customer, the request including a latency requirement. A provider substrate extension is selected to host the compute instance from a plurality of provider substrate extensions of the cloud provider network based at least in part on the latency requirement. The plurality of plurality of provider substrate extensions are connected to a communications service provider network and controlled at least in part by the service of the cloud provider network via a connection through the communications service provider network. A message is sent to cause the selected provider substrate extension to launch the compute instance for the customer.