Abstract: Disclosed techniques relate to managing power within a power distribution system. Power consumption corresponding to devices (e.g., servers) that receive power from an upstream device (e.g., a bus bar) may be monitored (e.g., by a service) to determine when power consumption corresponding to those devices breaches (or approaches) a budget threshold corresponding to an amount of power allocated to the upstream device. If the budget threshold is breached, or is likely to be breached, the service may initiate operations to distribute power caps for the devices and to initiate a timer. Although distributed, the power caps may be ignored by the devices until they are instructed to enforce the power caps (e.g., upon expiration of the timer). This allows the power consumption of the devices to exceed the budgeted power associated with the upstream device at least until expiration of the timer while avoiding power outage events.

Abstract: Techniques are described for enabling users of a cloud provider network to request the conditional termination of computing resources based on a forecasted availability of replacement capacity at a specified time or range of time in the future. A cloud provider network provides an application programming interface that can be used to make such requests, where the computing resources are hosted by the cloud provider network as part of a capacity pool shared by tenants of the cloud provider network. This type of request can be generated, for example, by a user desiring to terminate the use of some number of unproductive computing resources only if the user can be reasonably assured by the cloud provider network that capacity will be available at a future time when the user will likely need the capacity again.

Abstract: Techniques are described for providing service availability zones for computing-related services provided by a cloud provider network. According to some embodiments, the use of service availability zones enables users to achieve greater availability assurance for workloads sensitive to downtime or outages. The sensitivity of such workloads to downtime may be due to financial, regulatory, safety, or other reasons. Such availability-sensitive applications may in some cases be configured to run in multiple regions of a cloud provider network to increase their availability compared to running in a single availability zone. However, for some applications, the implementation of an application across multiple regions may not be feasible or desirable. The use of service availability zones provides user-visible fault domains within a single region of a cloud provider network, thereby enabling users to readily and reliably achieve application layer availability of approximately 99.

Abstract: A connectivity enablement device includes one or more processors, one or more memories and a hardware input port. The memories store program instructions that when executed examine a token obtained from a token transfer device inserted into the port, and cause one or more messages to be transmitted to a virtualized computing service. The messages indicate (a) the connectivity enablement device, (b) the token transfer device, (c) the token's source and (d) a server. An indication that the server has been configured within an isolated virtual network is obtained at the connectivity enablement device.

Abstract: Disclosed are various embodiments for a system that hardware locks a virtual machine to a host machine. The host machine can include a processor and a memory. A hypervisor can be stored in the memory that, when executed by the processor, causes the computing device to host one or more virtual machines. In addition, machine readable instructions stored in the memory that, when executed by the processor, cause the computing device to at least: receive a request to perform an operation on a virtual machine hosted by the hypervisor; evaluate the request to determine that the request complies with a policy; and in response to a determination that the request complies with the policy, cause the hypervisor to initiate the operation.

Abstract: Techniques are described for providing a multi-service storage layer in a cloud provider network for applications and workloads that are highly sensitive to outages affecting “mission critical” data or other resources. A multi-service storage layer is designed to provide additional resiliency against various types of correlated failures among existing geographic regions by enabling the storage of data using a plurality of separate storage services and storage resource types and across a plurality of regions of the cloud-provider network. A multi-service storage layer provides an application programming interface (API) with actions for storing, retrieving, and querying data stored in a highly available storage resource across a selection of underlying storage services.

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: Systems and methods are disclosed to implement a real-time data validation system that prevents problematic updates from being replicated from a primary database to a replica database. In embodiments, the data validation system injects a time delay into the replication process, so that when an update in a replication stream fails a specified data validation, the data validation system will prevent the update from being applied to the replica. In embodiments, the replication process is halted, a snapshot of the replica database is taken during the halt, and replication to the replica is resumed. Accordingly, if the problematic update is later confirmed to be invalid, the replica database can be rolled back to a point before the problematic update. Advantageously, the disclosed system can be used to implement a variety of data validations on top of a database replication process to protect the replica database from receiving undesired updates.

Abstract: Techniques are described that enable a cloud provider network to provide specialized regions that can be used to achieve greater availability assurance for workloads highly sensitive to downtime or outages. Cloud provider network users may use specialized regions to complement the use of provider network services offered in other geographic regions defined by the cloud provider network, either to host redundant computing resources or for failover purposes, where the operation of a specialized region is designed to provide additional resiliency against various types of correlated failures among the geographic regions. As one example, a cloud provider network may stage deployments of software updates to the web services provided by the cloud provider network in a manner that ensures that specialized regions receive such updates last and over a relatively long period of time, thereby helping to ensure that any software defects are detected in an earlier deployment of the update.

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: Systems and methods are disclosed to implement a real-time data validation system that prevents problematic updates from being replicated from a primary database to a replica database. In embodiments, the data validation system injects a time delay into the replication process, so that when an update in a replication stream fails a specified data validation, the data validation system will prevent the update from being applied to the replica. In embodiments, the replication process is halted, a snapshot of the replica database is taken during the halt, and replication to the replica is resumed. Accordingly, if the problematic update is later confirmed to be invalid, the replica database can be rolled back to a point before the problematic update. Advantageously, the disclosed system can be used to implement a variety of data validations on top of a database replication process to protect the replica database from receiving undesired updates.

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: Techniques for an optimization service of a service provider network to generate an architecture diagram that represents an architecture of a web-based application. The optimization service may use the architecture diagram to determine modifications or changes to make to the application. For example, the optimization service may compare the architecture diagram with optimized architecture diagrams that represent application best practices, and determine the modifications or change to make to the application to optimize the application and bring the application in-line with best practices. Further, the optimization service may use the architecture diagram to generate a visualization, and provide the user account with the visualization of the architecture diagram to show users their application architecture.

Abstract: Generally described, one or more aspects of the present application relate to deploying a software update to multiple clusters in a decentralized manner, where the individual clusters manage their own deployments based on successes and/or failures experienced by other clusters that have installed the software update. For example, a set of least conservative clusters may install the software update right away, whereas a set of more conservative clusters may wait and see how many of the clusters have installed the update so far and/or how the update is performing on those clusters, before installing the update themselves.

Abstract: A high-availability (HA) framework for services deployed in provider network environments. Services may be deployed as machine images or containers to a provider network. The HA framework provides a “wrapper” around the deployed services that provides feedback loops and flow control for inbound and outbound communications to other services on the provider network or to other external entities. The HA framework intercepts inbound and outbound traffic to the service, and may automatically determine, configure, and adjust networking management aspects such as timeouts, flow control, etc. for the service. The HA framework may also intercept outbound traffic to monitor outbound connections to other services to determine if the services satisfy HA requirements of the service.

Abstract: A computing resource service provider provides computing resources to customers, for example, computer system instances supported by server computer systems. These computer system instances may include logical volumes to support execution of the computer system instance. In addition, these instances may be terminated from time to time for various reasons. A stop signal transmitted to computing resource supporting a particular computer system instance may indicate that the particular computer system instance is to be terminated. In response to termination, the particular computer system instance may operate in accordance to a particular behavior.

Abstract: Techniques are described for providing a multi-service storage layer in a cloud provider network for applications and workloads that are highly sensitive to outages affecting “mission critical” data or other resources. A multi-service storage layer is designed to provide additional resiliency against various types of correlated failures among existing geographic regions by enabling the storage of data using a plurality of separate storage services and storage resource types and across a plurality of regions of the cloud-provider network. A multi-service storage layer provides an application programming interface (API) with actions for storing, retrieving, and querying data stored in a highly available storage resource across a selection of underlying storage services.

Abstract: Techniques are described for enabling users to create reservations for compute capacity at a service provider network intended for use in disaster recovery scenarios. A service provider can use separate geographic areas (sometimes referred to as “regions” or “availability zones”) defined by the service provider network to enable users to share reservations of compute capacity intended for use in disaster recovery scenarios. A disaster recovery launch reservation (DRLR) is a reservation of a given unit of compute capacity that is unique to a source geographic area (that is, a defined area of the service provider network containing computing resource(s) for which a user desires to obtain backup compute capacity) and a destination area (that is, a defined area of the service provider network at which the reserved compute capacity is located), where other users can reserve the compute capacity relative to other source geographic area-to-destination geographic area mappings.