Amazon Technologies, Inc.

James Michael Lamanna

Po-Chun Chen

Upendra Bhalchandra Shevade

Ethan Joseph Torretta

Sanjay Arunkumar Bhal

Justin Thomas Smith

Manish Gilani

Kim Thanh Do

Andrew Hemstreet Redmon

Erik Klayton Klavon

Halley Jagarapu

David Gonzales

Jagan Selvarajah

Vamsee Kasavajhala

Douglas Viana Esanbock

Benjamin Cory Schulz

In response to a programmatic request, configuration information representing a multi-network-segment gateway established on behalf of a customer is stored at a networking service. In response to another programmatic request, a communication session is established between a route signaling node of the gateway and a routing information source located at a customer premise. In response to additional programmatic input, the networking service stores an indication that the gateway is to be used to transfer packets between a cloud-side virtual network and a customer-side virtual network. The routing information exchanged in the session pertains to the cloud-side and customer-side virtual network, and is used to transfer data packets between the two virtual networks.

Custom configuration of cloud-based multi-network-segment gateways

A monitoring service transmits network packets from a user's source network segment to a user-defined endpoint upon request from a user. The endpoint can be any valid private IP address or DNS name where traffic is to be sent. Users can further define a monitor, which combines the endpoint, the subnets that the users want to send traffic from, and probes that define how packets are sent to the endpoint. Users can enable probe (IPv4 and IPv6) support, and probes can use ICMP or TCP protocols. Probes can be transmitted towards the configured endpoint from the source segments that are defined, and report metrics, such as packet loss and round-trip time or other measured latency. The metrics can be compared against health monitoring metrics to determine whether any issues are associated with a compute service provider, generally, or with a user network segment.

Network monitoring with correlation between user network segments and cloud provider resources

During a communication session established with a customer-premise routing information source, a route signaling node of a multi-network-segment gateway of a cloud provider network obtains respective sets of labeled routing information pertaining to multiple customer-side network segments of a customer. The route signaling node propagates the routing information to data plane nodes of the gateway. The data plane nodes utilize the routing information to forward data packets to destinations associated with particular customer-side network segments.

Software-defined multi-network-segment gateways for scalable routing of traffic between customer-premise network segments and cloud-based virtual networks

The following description is directed to configuring gateways in computer networks. For example, a method includes receiving a first request from a client associated with a configurable network. The first request can request associating a set of network addresses assigned to the configurable network to a gateway. A second request can be received from a client associated with the gateway. The second request can request accepting the association of the first request. It can be determined that the set of network addresses do not overlap with a network address space that is accessible using the gateway. Routing information can be generated for the gateway. The generated routing information can be used to configure the gateway for forwarding network packets between the client private network and the configurable network.

Multi-account gateway

Technologies are provided for expanding computer network route advertisements. A route expansion server can be configured to receive route advertisements from a router, generate an expanded route advertisement that includes additional network route information, and transmit the expanded route advertisement to another router. The route expansion server can receive a route advertisement from a network zone edge router, comprising a network address prefix. The route expansion server can look up one or more additional network address prefixes associated with the edge router and generate an expanded route advertisement message that indicates that the edge router is a potential next hop for the network address prefix and the one or more additional network address prefixes. The route expansion server can transmit the expanded route advertisement message to another router. In at least some embodiments, the route expansion server can generate different expanded route advertisement messages for different routers.

Network route expansion

A physical interconnect having multiple virtual paths is coupled between network devices of independent networks operated by different entities. In one aspect, the interconnect is monitored so that the entities can simultaneously and separately monitor network traffic being exchanged across the interconnect. Each entity can be assigned two virtual paths through the interconnect to pass network traffic through their network device, over the interconnect, through a network device of the other entity, back over the interconnect link and back through their network device. The network devices can be configured to loop back network packets using a variety of loopback configurations. Hardware policers that monitor capacity usage of the virtual paths can also be tested.

Growing community of inventors

Round Hill, VA, United States of America

James Michael Lamanna