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: A network-based service may schedule requests received from clients according to information regarding prior requests from the client included the requests. When a request is received at a network-based service, information regarding the request, and possibly other prior requests, may be included in response for the request sent to the client. The client may then include that information in a subsequent request to the network-based service. An evaluation of the information may determine a scheduling decision for the request and the request may then be processed according to the scheduling decision.

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 are described for optimizing the allocation of computing resources provided by a service provider network—for example, compute resources such as virtual machine (VM) instances, containers, standalone servers, and possibly other types of computing resources—among computing workloads associated with a user or group of users of the service provider network. A service provider network provides various tools and interfaces to help businesses and other organizations optimize the utilization of computing resource pools obtained by the organizations from the service provider network, including the ability to efficiently schedule use of the resources among workloads having varying resource demands, usage patterns, relative priorities, execution deadlines, or combinations thereof. A service provider network further provides various graphical user interfaces (GUIs) to help users visualize and manage the historical and scheduled uses of computing resources by users' workloads according to user preferences.

Abstract: Techniques are described for optimizing the allocation of computing resources provided by a service provider network—for example, compute resources such as virtual machine (VM) instances, containers, standalone servers, and possibly other types of computing resources—among computing workloads associated with a user or group of users of the service provider network. A service provider network provides various tools and interfaces to help businesses and other organizations optimize the utilization of computing resource pools obtained by the organizations from the service provider network, including the ability to efficiently schedule use of the resources among workloads having varying resource demands, usage patterns, relative priorities, execution deadlines, or combinations thereof. A service provider network further provides various graphical user interfaces (GUIs) to help users visualize and manage the historical and scheduled uses of computing resources by users' workloads according to user preferences.

Abstract: Techniques are described for optimizing the allocation of computing resources provided by a service provider network—for example, compute resources such as virtual machine (VM) instances, containers, standalone servers, and possibly other types of computing resources—among computing workloads associated with a user or group of users of the service provider network. A service provider network provides various tools and interfaces to help businesses and other organizations optimize the utilization of computing resource pools obtained by the organizations from the service provider network, including the ability to efficiently schedule use of the resources among workloads having varying resource demands, usage patterns, relative priorities, execution deadlines, or combinations thereof. A service provider network further provides various graphical user interfaces (GUIs) to help users visualize and manage the historical and scheduled uses of computing resources by users' workloads according to user preferences.

Abstract: A method for launching a plurality of computing instances may include obtaining a request to launch a plurality of computing instances. The request may indicate a first number and a target number of compute instances that is larger than the first number. The method may further include verifying that there is sufficient capacity, for example of a compute instance service, to launch at least the first number of compute instances. The request may be fulfilled by at least launching at least the first number of compute instances in a way that bypasses a rate limit that limits a rate at which compute instances can be launched. In some cases, the method may additionally include launching additional compute instances, as they become available, until the target number has been reached.

Abstract: A service workflow agent associated with a particular service of a provider network identifies a repository in which workflow descriptors indicative of tasks to be performed by the service are stored. In response to determining that a modification has been applied at one such repository, the agent examines a particular workflow descriptor stored in the repository. The agent initiates an attempt to implement a first task indicated in the descriptor. Subsequently, the agent updates the descriptor in accordance with an optimistic concurrency control technique to indicate a status of the first task.

Abstract: Techniques for private network mirroring are described. Users can select one or more existing private networks to be mirrored in the same or different network area. Any network configuration changes made in the selected private network (e.g., “master” private network) can be propagated automatically to the mirror private network. This enables users to utilize resources in another network area for disaster recovery, ensuring that the network configuration of the mirror private network is consistent with the master private network through real-time updates. Additionally, users managing infrastructure that includes multiple private networks can select one master private network and propagate configuration changes to other private networks, reducing management overhead incurred by these multi-private network installations.

Abstract: Techniques for private network mirroring are described. Users can select one or more existing private networks to be mirrored in the same or different network area. Any network configuration changes made in the selected private network (e.g., “master” private network) can be propagated automatically to the mirror private network. This enables users to utilize resources in another network area for disaster recovery, ensuring that the network configuration of the mirror private network is consistent with the master private network through real-time updates. Additionally, users managing infrastructure that includes multiple private networks can select one master private network and propagate configuration changes to other private networks, reducing management overhead incurred by these multi-private network installations.

Abstract: A system and method for client authentication wherein a client computing system is authenticated by at least performing, at an authentication system different than a target computing system, a set of validation operations on authorization information addressed to a destination port of the target computing system, and, as a result of the client computing system being authenticated by the set of validation operations, switching to a mode wherein a port of the target computing system is opened and data from the client computing system is communicated to the port of the target computing system.

Abstract: Various systems, processes, and techniques may be used to allocate computer resources. In particular implementations, systems and processes for allocation of computer resources may include the ability to determine whether a request for allocation of computer resources has been received and determine a set of server computers able to fulfill requirements of the request. The systems and processes may also include the ability to identify one or more server computers in the set likely to successfully provide the computer resources and allocate the requested computer resources on an identified server computer.

Abstract: In a service provider environment, software deployments can be implemented by automatically routing an incrementally larger percentage of requests to a new software stack based on a success rate for previous requests. Thus, new and old versions of the software stack can be executed simultaneously with a small portion being routed to the new version until a sufficient number of requests have been handled. By slowly bringing a new software stack online, a confidence level in the new deployment can increase until it is fully deployed. Different success rates and different ramping rates can be used for each customer or based on different components of the request, such as API name, API parameters, location, etc. The software deployments can be extended to web-page requests.

Abstract: Methods and systems for a topology service providing an interface for specifying a topology and answering queries regarding the topology. Further, the topology service may create, from a specified topology, a directed acyclic graph and corresponding closure table. The topology service may also provide an interface for receiving metadata regarding the topology. In this way, the topology service, based at least in part on connections between nodes in the entries of the closure table and based at least in part on the metadata regarding the topology, may answer queries in regard to the specified topology.

Abstract: At a logging service, a representation of a transaction requested by a client is received. The transaction includes at least a first write operation directed to a data object at a first data store. Based at least in part on the contents of the representation and contents of a persistent log of the logging service, a determination is made that the requested transaction is to be committed. A log record corresponding to the first write operation is inserted into the persistent log. The first write is propagated to the first data store after the record has been inserted in the persistent log.

Abstract: At a logging service, a representation of a transaction requested by a client is received. The transaction includes at least a first write operation directed to a data object at a first data store. Based at least in part on the contents of the representation and contents of a persistent log of the logging service, a determination is made that the requested transaction is to be committed. A log record corresponding to the first write operation is inserted into the persistent log. The first write is propagated to the first data store after the record has been inserted in the persistent log.

Abstract: A technology is described for providing a nondeterministic value to computing instances executing an application as part of a high availability system. An example method may include receiving a request for a nondeterministic value at a physical host that hosts a first computing instance, where the request may be for an application executing on the first computing instance. A nondeterministic value may be obtained from a nondeterministic value source located on the physical host and provided to the application executing on the first computing instance. A second request from a second computing instance may be received at the physical host, where the second request may be associated with a copy of the application executing on the second computing instance. The nondeterministic value may then be identified in the computer memory of the physical host and provided to the second computing instance over a computer network.

Abstract: Deployment feedback for updates to resources implemented in a private network may be implemented. Feedback codes may be generated and included in deployments sent to a private network for deployment at resources implemented in the private network. One or more of the included feedback codes may be selected based on the performance of the deployment and provided via a feedback communication channel that is disconnected and distinct from the private network. Once received, a current status of the deployment may be determined based on the one or more feedback codes provided via the feedback communication channel.

Abstract: Methods and apparatus for providing scalable private services in service provider networking environments. A service provider that provides a large, public, multi-tenant implementation of a web service to multiple customers via a public API endpoint may allow a customer to request the establishment of a private implementation of the service. In response, a service private instance may be automatically and/or manually established for the customer that provides a private API endpoint to the service and that is at least in part implemented on single-tenant hardware that is not shared with other customers. The service private instance may initially be implemented as a relatively small scale and possibly limited implementation of the service when compared to the service public instance. As the needs of the customer grow, the service private instance may be automatically and/or manually scaled up from the initial implementation.

Abstract: At a logging service, a representation of a transaction requested by a client is received. The transaction includes at least a first write operation directed to a data object at a first data store. Based at least in part on the contents of the representation and contents of a persistent log of the logging service, a determination is made that the requested transaction is to be committed. A log record corresponding to the first write operation is inserted into the persistent log. The first write is propagated to the first data store after the record has been inserted in the persistent log.