Abstract: Route tables may be associated with ingress traffic for logically isolated networks. A routing device at the edge of a logically isolated network may receive a route to include in a route table that is associated with ingress traffic to the logically isolated network to forward the ingress traffic to a network appliance hosted in the logically isolated network. Network packets received at the edge routing device may have a destination of a computing resource hosted in the logically isolated network. The edge routing device may identify the route in the route table to override the destination in the network packet with the network appliance and forward the network packet to the network appliance according to the route.

Abstract: Techniques are described for managing customer-specified routing policies for network-accessible computing resources. In some situations, the customer-specified routing policies may be based at least in part on DNS (“Domain Name System”) information specified by a customer, such as if the customer specifies one or more target destinations to use with an indicated DNS domain name that are different from the destination IP address(es) provided for that DNS domain name by DNS servers—if so, the managing of such a DNS-based routing policy for that customer may include identifying when network-accessible computing resources provided to the customer send electronic communications to that DNS domain name, and causing those electronic communications to be redirected to the customer-specified target destination(s). Such customer-specified target destinations may include, in different situations, final destinations, intermediate destinations, etc., as well as identify particular routes.

Abstract: A facility for estimating a value relating to an occurrence is described. The facility receives a first occurrence specifying a first value for each of a plurality of independent variables that include a distinguished independent variable designated to be monotonically linked to a dependent variable. The facility subjects the first independent variable values specified by the received occurrence to a statistical model to obtain a first value of the dependent variable. The facility receives a second occurrence specifying a second value for each of the plurality of independent variables (the second values varying from the first values in a first direction). The facility subjects the second independent variable values to the statistical model to obtain a second value of the dependent variable, the second value of the dependent variable being guaranteed not to vary from the first value of the dependent variable in a second direction opposite the first direction.

Abstract: Techniques are disclosed for determining for determining parameters for a Transmission Control Protocol (TCP) connection between two computing nodes before the connection is established. In embodiments, the latency of data transmission between two computing nodes and the throughput capacity of a network link are measured, and from this data, TCP parameters for a future network connection between two computing nodes are determined. This information is sent to a TCP stack that stores it in its route table. Then, the TCP stack uses TCP parameters based on the information stored in the route table.

Abstract: A control-plane component of a virtual network interface (VNI) multiplexing service assigns one or more VNIs as members of a first interface group. A first VNI of the interface group is attached to a first compute instance. Network traffic directed to a particular endpoint address associated with the first interface group is to be distributed among members of the first interface group by client-side components of the service. The control-plane component propagates membership metadata of the first interface group to the client-side components. In response to a detection of an unhealthy state of the first compute instance, the first VNI is attached to a different compute instance by the control-plane component.

Abstract: A customer may request a service endpoint for a service in their virtual network on a provider network. In response, a service endpoint is generated in the customer's virtual network, a local IP address in the IP address range of the customer's virtual network is assigned to the service endpoint, and a DNS name is assigned to the service endpoint. Resources on the customer's virtual network resolve the DNS name of the service endpoint to obtain the local IP address of the service endpoint and send service requests for the service to the local IP address of the service endpoint. The service endpoint adds routing information to the service requests and sends the service requests over the network substrate to be routed to the service.

Abstract: The present invention concerns enriched heterogeneous mammalian renal cell populations characterized by biomarkers, and methods of making and using the same.

Abstract: A method and apparatus for rate limiting network traffic are provided. A plurality of network devices may receive network traffic and route the network traffic to a destination. Rate limits may be imposed on the output rate of the plurality of network devices. The rate limits may be adjusted as the flow of the network traffic changes.

Abstract: Methods and apparatus that allow clients to connect resource instances to virtual networks in provider network environments via private IP. Via private IP linking methods and apparatus, a client of a provider network can establish private IP communications between the client's resource instances on the provider network and the client's resource instances provisioned in the client's virtual network via links from the private IP address space of the virtual network to the private IP address space of the provider network. The provider network client resource instances remain part of the client's provider network implementation and may thus also communicate with other resource instances on the provider network and/or with entities on external networks via public IP while communicating with the virtual network resource instances via private IP.

Abstract: In accordance with a designation of a private alias endpoint as a routing target for traffic directed to a service from within an isolated virtual network of a provider network, a tunneling intermediary receives a baseline packet generated at a compute instance. The baseline packet indicates a public IP (Internet Protocol) address of the service as the destination, and a private IP address of the compute instance as the source. In accordance with a tunneling protocol, the tunneling intermediary generates an encapsulation packet comprising at least a portion of the baseline packet and a header indicating the isolated virtual network. The encapsulation packet is transmitted to a node of the service.

Abstract: Methods and apparatus that allow clients to connect resource instances to virtual networks in provider network environments via private IP. Via private IP linking methods and apparatus, a client of a provider network can establish private IP communications between the client's resource instances on the provider network and the client's resource instances provisioned in the client's virtual network via links from the private IP address space of the virtual network to the private IP address space of the provider network. The provider network client resource instances remain part of the client's provider network implementation and may thus also communicate with other resource instances on the provider network and/or with entities on external networks via public IP while communicating with the virtual network resource instances via private IP.

Abstract: The present invention concerns enriched heterogeneous mammalian renal cell populations characterized by biomarkers, and methods of making and using the same.

Abstract: A control-plane component of a virtual network interface (VNI) multiplexing service assigns one or more VNIs as members of a first interface group. A first VNI of the interface group is attached to a first compute instance. Network traffic directed to a particular endpoint address associated with the first interface group is to be distributed among members of the first interface group by client-side components of the service. The control-plane component propagates membership metadata of the first interface group to the client-side components. In response to a detection of an unhealthy state of the first compute instance, the first VNI is attached to a different compute instance by the control-plane component.

Abstract: A facility for estimating the cost of a remodeling project is described. The facility accesses a project cost model that predicts project costs determined from a photograph based upon project characteristics. The facility applies the access project cost model to characteristics of a distinguished project to obtain an estimated cost. The facility causes the obtained estimated cost to be displayed.

Abstract: Methods and apparatus for private network peering in virtual network environments in which peerings between virtual client private networks on a provider network may be established by clients via an API to a peering service. The peering service and API 104 may allow clients to dynamically establish and manage virtual network transit centers on the provider network at which virtual ports may be established and configured, virtual peerings between private networks may be requested and, if accepted, established, and routing information for the peerings may be specified and exchanged. Once a virtual peering between client private networks is established, packets may be exchanged between the respective client private networks via the peering over the network substrate according to the overlay network technology used by the provider network, for example an encapsulation protocol technology.

Abstract: In the event of loss of connection (4) between an access point (3) and a data network (5), the access point (3) transmits instructions to a data processing device (1) connected to the access point (3) to cause the data processing device (1) to re-establish connection to the data network (5) by another means. These instructions cause the data processing device to scan for beacon signals from further wireless access points, and establish connection (7, 8) to the data network (5) through a wireless access point (6) identified in the scanning process.

Abstract: In accordance with a designation of a private alias endpoint as a routing target for traffic directed to a service from within an isolated virtual network of a provider network, a tunneling intermediary receives a baseline packet generated at a compute instance. The baseline packet indicates a public IP (Internet Protocol) address of the service as the destination, and a private IP address of the compute instance as the source. In accordance with a tunneling protocol, the tunneling intermediary generates an encapsulation packet comprising at least a portion of the baseline packet and a header indicating the isolated virtual network. The encapsulation packet is transmitted to a node of the service.

Abstract: In various methods and apparatus Internet Protocol (IP) addresses can be moved between virtual machine instances in a provider network. Customers can cause an IP address to be moved between virtual machine instances such as by submitting an application programming interface call. The provider network also may include a server system that implements the dynamic host configuration protocol such as the DHCP for version 6. The DHCP server system moves the requested IP address by exchanging messages with the effected instances. The DHCP server system may transmit a message to remove the IP address from a first instance by including the IP address with a valid lifetime set to a minimal time-out value. The DHCP server system may transmit a message to add the IP address to a second instance by including the IP address and a corresponding valid lifetime value of greater than the minimal time-out value.

Abstract: A control-plane component of a virtual network interface (VNI) multiplexing service assigns one or more VNIs as members of a first interface group. A first VNI of the interface group is attached to a first compute instance. Network traffic directed to a particular endpoint address associated with the first interface group is to be distributed among members of the first interface group by client-side components of the service. The control-plane component propagates membership metadata of the first interface group to the client-side components. In response to a detection of an unhealthy state of the first compute instance, the first VNI is attached to a different compute instance by the control-plane component.