Abstract: Disclosed are systems and methods that provide a computerized device management framework that adaptively determines and applies security and configuration parameters to a device on a first network, and enables the adaptive application of such parameters as the device disconnects and connects to other networks. The disclosed framework enables the automatic detection of different networks being relied upon by the device for access to the Internet, upon which, management control policies of the device's activities can be controlled and managed in a unified manner. Accordingly, the disclosed framework can enable security and configuration mechanisms applied on a first network, upon which they are associated, to be seamlessly applied on another disparate network via a virtual private network connection enabled via proprietary mechanisms implemented on the device.

Abstract: Techniques and technologies for migrating workloads between different VM instance types based on changes in resource utilization over a period of time. Selecting one VM instance type to host workloads can result in use of a VM instance type that is optimized for the workload during one timeframe of a period of time, but is over-provisioned or under-provisioned for the workload during another timeframe of a period of time. Accordingly, a service provider network may analyze historical utilization patterns of workloads over a period of time, and identify different VM instance types that are optimized for the workloads during different timeframes of the period of time. The service provider network may then cause the workloads to be migrated between the different VM instance types over the period of time such that the workloads are hosted on VM instances that are optimized for the current resource utilization of the workloads.

Abstract: Generally described, one or more aspects of the present application relate to an instance cloning service for cloning a running virtual machine instance and configuring the resources of the new virtual machine instance created by cloning the running virtual machine instance. For example, the instance cloning service can create the new virtual machine instance and attach it to a storage volume to which the original virtual machine instance is attached. The instance cloning service may subsequently move the new virtual machine instance to another storage volume (e.g., based on a user request or based on the performance of the instances). Alternatively, upon cloning, the instance cloning service may attach the new virtual machine instance to a new storage volume. For example, the instance cloning service may use copy-on-write to provide the new virtual machine instance with its own storage volume.

Abstract: Disclosed are various embodiments for an emulation layer for overcoming incompatibilities in virtual machine instance migration. In one embodiment, a virtual machine instance configured for a first computing architecture is executed in a first computing device having the first computing architecture. The virtual machine instance from the first computing device is migrated to a second computing device having a second computing architecture. The virtual machine instance is executed in the second computing device using an emulation layer that emulates the first computing architecture in the second computing architecture.

Abstract: This disclosure leverages multi-attach to block store volumes for more reliable live migration of virtualized resources. A block storage client of a virtualized resource operating on a source host in a first data center can be attached to a block storage volume stored on block storage hosts in the first data center. State data associated with the virtual machine can be transmitted from the source host to a target host, after which the virtual machine can run on the target host and operations of the virtualized resources may be ceased on the source host. Failure of the migration may require roll back to the source host. The source host may remain connected to the volume while the target host client connects to the volume, such that the volume may be accessed by the block storage client on the source host after rollback to provide uninterrupted operation of the virtual machine.

Abstract: Disclosed are various embodiments for locality-based network slicing in radio-based networks. In one embodiment, network traffic is received via a network slice in a radio-based network. The radio-based network includes a radio access network and an associated core network. The network slice is associated with at least one locality rule requiring that the network traffic remain within a particular geographic area. It is determined that the radio-based network has resources to comply with the locality rule(s). The network traffic in the radio-based network is acted upon in order to comply with the locality rule(s).

Abstract: Disclosed are various embodiments for provisioning radio-based networks with locality rules. In one embodiment, at least one locality rule associated with an organization is accessed. The locality rule(s) require that at least a subset of network traffic for a radio-based network remain within a particular geographic area. The radio-based network includes a radio access network and an associated core network. A topology for the radio-based network is determined based at least in part on the locality rule(s). The radio-based network is provisioned or reconfigured for the organization to have the topology complying with the at least one locality rule.

Abstract: Techniques for a device with NUMA a memory architecture to migrate virtual resources between NUMA nodes to reduce resource contention between virtual resources running on the NUMA nodes. In some examples, the device monitors various metrics and/or operations of the NUMA nodes and/or virtual resources, and detect events that indicate that virtual resources running on a same NUMA node are contending, or are likely to contend, for computing resources of the NUMA node. Upon detecting such an event, the device may migrate a virtual resource from the NUMA node to another NUMA node on the device that has an availability of computing resources. The device may then migrate the virtual resource from the overcommitted NUMA node onto the NUMA node that has availability to run the virtual resource. In this way, devices may reduce resource contention among virtual resources running on a same NUMA node.

Abstract: This disclosure describes systems, devices, and techniques for migrating virtualized resources between the main region and edge locations. Live migration enables virtualized resources to remain operational during migration. Edge locations are typically separated from secure data centers via the Internet, a direct connection, or some other intermediate network. Accordingly, to place virtualized resources within an edge location, the virtualized resources must be migrated over a secure communication tunnel that can protect virtualized resource data during transmission over the intermediate network. The secure communication tunnel may have limited data throughput. To efficiently utilize resources of the secure communication tunnel, and to reduce the impact of migrations on virtualized resource operations, virtualized resource migrations may be carefully scheduled in advance.

Abstract: Various techniques for managing heat and backwards-incompatible updates in cloud-based networks are described. In an example method, a virtualized resource, is identified. At least one first host may include an updated version of an element and at least one second host may include a previous version of the element. The updated version may be incompatible with the previous version. A first desirability index corresponding to the at least one first host may be less than a second desirability index corresponding to the at least one second host. The virtualized resource may be live-migrated from the source host to a target host among the at least one first host.

Abstract: This disclosure describes systems, devices, and techniques for migrating virtualized resources from outdated hosts during requested reboots of the virtualized resources, in order to update the outdated hosts. In an example method, a pending reboot a virtualized resource occupying a first host can be identified. At least one component of the first host may be determined to be outdated. In response to identifying the pending reboot and determining that the at least one component is outdated, the virtualized resource may be migrated to a second host. The first host may update the at least one component.

Abstract: This disclosure describes systems, devices, and techniques for quick restarts of virtualized resources hosted by a cloud-based network. In an example method, a request to restart a virtualized resource hosted by a first server can be received. A second server, with a capacity to host the virtualized resource, may be identified. In response to identifying the second server, the virtualized resource can be migrated from the first server to the second server. A message confirming that the virtualized resource has been restarted may be transmitted.

Abstract: This disclosure describes systems, devices, and techniques for live migrating virtualized resources between the main region and edge locations. Live migration enables virtualized resources to remain operational during migration. Edge locations are typically separated from secure data centers via the Internet, a direct connection, or some other intermediate network. Accordingly, to place virtualized resources within an edge location, the virtualized resources must be migrated over a secure communication tunnel that can protect virtualized resource data during transmission over the intermediate network. The secure communication tunnel may have limited data throughput. To efficiently utilize resources of the secure communication tunnel, virtualized resource data may be transferred over the tunnel in a two-stage process.

Abstract: Snapshots of instance store volumes may be automatically obtained prior to an upcoming migration event for an associated VM instance(s). This automated snapshotting allows customers to restore their data from the snapshot of their instance store volumes in the event of a failure during the migration event that results in an inability to start (or launch) the customer's VM instance on a target host computer. In an example process, a computing device(s) may determine that a migration event is scheduled to be performed for a VM instance, determine that the VM instance is associated with one or more instance store volumes, obtain a snapshot of the one or more instance store volumes, and store the snapshot in storage of a network-based storage service prior to performing the migration event. In some embodiments, the snapshot may be stored in association with a service provider account of the network-based storage service.

Abstract: This disclosure describes techniques for flexible maintenance windows for performing maintenance for instances. Using techniques described herein, a user of a service provider network may specify configuration data that relates to maintenance events of instances. A “maintenance event” is any event that relates to deploying instances and/or at least temporarily losing use of an instance. For example, a maintenance event may cause an instance to be deployed, re-booted, re-started, or replaced. According to some configurations, customers may specify one or more maintenance event windows for when maintenance is to be performed, as well as customize notifications that are provided to the customer about scheduled maintenance events. For instance, customers may create a maintenance window that specifies to perform maintenance on Tuesdays, between 2 AM-3 AM, and that notifications are to include information specified by the customer (e.g., through one or more tags).

Abstract: Generally described, one or more aspects of the present application relate to an instance resource oversubscription service for scheduling a burst period for a running virtual machine instance based on a time window specified by a user of the virtual machine instance. For example, the instance resource oversubscription service can predict future resource usage and identify the appropriate timing and physical host machine for letting the user burst (e.g., temporarily use the virtual machine instance in a manner than consumes a higher amount of computing resources such as CPU cycles, memory, network bandwidth, etc.). In doing so, the instance resource oversubscription service may consider, for example, the historical and current resource utilization levels of the virtual machine instances running on a set of available physical host machines and the burst period scheduling requests from other users of the instance resource oversubscription service.

Abstract: Methods and apparatus for post data synchronization in live migration of domains. Host devices on a network may implement virtual machines (VMs) as domains in an execution environment, and may provide local persistent storage for data of the VMs. A migration technique for moving a domain including the persistent data from one host device to another host device is described in which the VM is instantiated on the target device, and the domain is switched to the target device. Synchronization of the VM's data from the persistent storage on the source device to the target device is then initiated, for example according to a distributed replicated storage technique that makes the target device's persistent storage the primary storage and the source device's persistent storage the secondary storage for the VM. Once the data is synchronized, the VM and its respective storage on the source device are released.

Abstract: Methods and apparatus for post data synchronization in live migration of domains. Host devices on a network may implement virtual machines (VMs) as domains in an execution environment, and may provide local persistent storage for data of the VMs. A migration technique for moving a domain including the persistent data from one host device to another host device is described in which the VM is instantiated on the target device, and the domain is switched to the target device. Synchronization of the VM's data from the persistent storage on the source device to the target device is then initiated, for example according to a distributed replicated storage technique that makes the target device's persistent storage the primary storage and the source device's persistent storage the secondary storage for the VM. Once the data is synchronized, the VM and its respective storage on the source device are released.

Abstract: Methods and apparatus for post data synchronization in live migration of domains. Host devices on a network may implement virtual machines (VMs) as domains in an execution environment, and may provide local persistent storage for data of the VMs. A migration technique for moving a domain including the persistent data from one host device to another host device is described in which the VM is instantiated on the target device, and the domain is switched to the target device. Synchronization of the VM's data from the persistent storage on the source device to the target device is then initiated, for example according to a distributed replicated storage technique that makes the target device's persistent storage the primary storage and the source device's persistent storage the secondary storage for the VM. Once the data is synchronized, the VM and its respective storage on the source device are released.

Abstract: Techniques for managing large-scale automatic fleet refresh operations are described herein. An application programming interface request to perform a refresh operation on a set of computer system instances is received. The application programming interface request includes a set of constraints for performing the refresh operation which are used to determine the impact of performing the refresh operation. Based at least in part on the impact, a set of schedules for performing the refresh operation is provided.