Abstract: At a managed control plane service, constituent services and operational requirements of an application are identified. In response to an end-user request directed to the application, contents of an inter-service request are generated at a resource selected by the managed control plane service for a first constituent service, and a response to the message is generated at another resource selected for a second constituent service. Tasks to be performed for the operational requirements are initiated by the managed control plane service.

Abstract: Techniques are described for establishing connectivity between compute instances hosted by an edge location of a cloud provider network (also referred to as a provider network substrate extension (PSE)) deployed within a communications service provider (CSP) network and the communications service provider network. A compute instance is hosted on a PSE of a cloud provider network, the PSE connected to a CSP network. A first network address is assigned to the compute instance from a pool of network addresses of the CSP network. A gateway of the PSE is updated to direct packets addressed to the first network address to the compute instance.

Abstract: A number of cells of a control plane of a virtualized computing service are set up, including a first cell with one or more request processing nodes, a local instance of a data store, and metadata indicating a set of virtualization hosts. A request processer transmits a request for a virtual machine to the first cell. A request processor of the cell initiates a workflow to launch the virtual machine using a virtualization host; the workflow includes storing a record of the request in the local instance of the data store.

Abstract: Techniques are described for enabling users to configure the auto scaling of virtual computing resources using various intent-based auto scaling configurations. Intent-based configurations generally provide various indications of how a user intends to use a scalable group of virtual computing resources and what expectations a user might have about how those resources are scaled in response to changes in demand. A service provider network receives first input to create a scalable group of virtualized computing resources, the first input indicating at least one primary scaling configuration used by the hardware virtualization service to scale the scalable group of compute instances over time, and further receives second input indicating at least one secondary, intent-based scaling configuration used to scale the virtualized computing resources, for example, when the service is unable to scale the group of virtualized computing resources according to the at least one primary scaling condition.

Abstract: Techniques are described for enabling customers of a service provider network to modify and extend the functionality of application programming interfaces (APIs) provided to customers by various services of the provider network. Services of a service provider network provide interfaces that enable customers and other users to define custom API actions representing functionality to be performed by the services upon receipt of corresponding API requests. In this manner, the functionality exposed by provider network services to customers via APIs becomes extensible and customizable to fit customers' particular use cases and without the provider network needing to contemplate and explicitly implement all possible customer-specific API action variations.

Abstract: Techniques for API-based endpoint discovery involving provider substrate extension resources are described. A discovery coordinator service located within the provider network can identify one or more endpoints from a set of potentially distributed endpoints for a client to utilize, where endpoints may be located within provider substrate extensions of the provider network. The discovery coordinator service can utilize location values of the client provided via an API request, such as its network address or geographic coordinates, to identify a nearby resource that may be most optimal for the client to use via providing minimal latency of access.

Abstract: A first virtualization control mode to be used for configuring one or more compute instances is determined. Based at least partly on the mode, preparatory configuration operations for launching a compute instance are initiated. The operations include transferring at least a portion of a machine image to a storage device accessible from a host, and initialization of a virtual network interface. A compute instance is instantiated using the machine image at the host. The compute instance is a thread of an intermediary process launched by an administrative agent at the host in response to a launch request.

Abstract: A system and method for managing a computer-implemented online game provides dynamically variable rewards to incentivize player interaction with sponsored content presented within the game. The particular reward offered to incentivize player interaction with particular sponsored content (e.g., a particular advertisement) can be dynamically variable based on the attributes of the player, thus providing user-specific custom rewards for interaction with sponsored content. Properties of incentive rewards that may be dynamically variable can include a custom type of in-game asset or resource, and/or a custom amount of a particular in-game asset or resource.

Abstract: A number of cells of a control plane of a virtualized computing service are set up, including a first cell with one or more request processing nodes, a local instance of a data store, and metadata indicating a set of virtualization hosts. A request processer transmits a request for a virtual machine to the first cell. A request processor of the cell initiates a workflow to launch the virtual machine using a virtualization host; the workflow includes storing a record of the request in the local instance of the data store.

Abstract: Techniques are described for enabling users of a cloud provider network to discover “availability groups” provided by a cloud provider network and to request the launch of computing resources into selected availability groups. Some cloud provider networks are expanding the definition of traditional “availability zones” to include new types of availability zones representing various types of provider substrate extension edge locations—including, for example, cloud-provider managed substrate extensions associated with separate control planes, 5G-enabled provider substrate extensions connected to communications service provider networks, and the like. Availability groups can be used to represent various defined collections these new types of provider substrate extensions, where each availability group may be defined such that includes a set of provider substrate extensions with a similar set of characteristics and capabilities.

Abstract: A first request to reserve a quantity of resources that comply with a constraint specified in the first request is obtained. A set of available resources that fulfills the constraint is determined based on current capacity usage. A token is associated with the set of available resources, with the token being associated with an expiration. The quantity of resources from the set of available resources is reserved, where the quantity allocated is unavailable, until the expiration, to fulfill resource requests that lack the token. The token is provided in response to the first request.

Abstract: Techniques for on demand capacity management in a provider network are described. The provider network includes electronic devices that provide computing-related resources to customers. The unused capacity of these electronic devices—such as processor cores, memory, network bandwidth, etc.—can be used to satisfy a variety of computing needs. Services of the provider network allocate portions of the unused capacity based on customer requests for computing-related resources.

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: 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 system and methods are disclosed for adding slots to a group of slots for instantiating compute instances. Compute capacity of a computing system of a plurality of computing systems is detected. A first slot and a second slot of the group of slots are determined based on compute instances instantiated on the computing systems. The first slot is associated with a first type of compute instance and the second slot is associated with a second type of compute instance. The first type of compute instance and the second type of compute instance have different computing resource values associated therewith. The first slot and the second slot are added to the group of slots for respectively instantiating the first type and the second type of compute instances.

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.

Abstract: Techniques for managing the migration of virtual machine instances are described herein. A migration of a first virtual machine instance is started by preparing an appropriate target location to receive the first virtual machine instance. Next, a second virtual machine instance at the target location is enabled by first copying state information from the first virtual machine instance to the second virtual machine instance, by next creating connections between the second virtual machine instance and resources associated with the first virtual machine instance, and by finally starting packet forwarding between the two virtual machine instances. Finally, the first virtual machine instance is locked, the copy is finalized, and the second virtual machine instance is started.

Abstract: Techniques for reducing latency between resources of a cloud provider network and end user devices are described. In one embodiment, a system includes a cloud provider network including a first control plane service to manage customer compute instances hosted on resources of the cloud provider network. The system further includes a first provider substrate extension of the cloud provider network connected to a first communications service provider network. The first provider substrate extension includes a first computer system having capacity for executing customer compute instances, is controlled at least in part by the first control plane service via a connection through at least a portion of the first communications service provider network, executes at least a first customer compute instance using the first computer system, wherein the first customer compute instance communicates with a first mobile computer system connected via the first communications service provider network.

Abstract: A first virtualization control mode to be used for configuring one or more compute instances is determined. Based at least partly on the mode, preparatory configuration operations for launching a compute instance are initiated. The operations include transferring at least a portion of a machine image to a storage device accessible from a host, and initialization of a virtual network interface. A compute instance is instantiated using the machine image at the host. The compute instance is a thread of an intermediary process launched by an administrative agent at the host in response to a launch request.