Route advertisement management using tags in directly connected networks
First Claim
1. A system comprising:
- a provider network comprising a plurality of physical computing devices configured to implement resources of the provider network; and
an endpoint router of the provider network, wherein the endpoint router is connected to a client network of a client of the provider network via a dedicated physical connection between the provider network and the client network,wherein one or more networking devices of the provider network are configured to;
receive, via the endpoint router, a routing protocol message from the client network, wherein the routing protocol message comprises;
one or more respective routes for devices of the client network; and
one or more respective tag fields populated with respective values, wherein respective ones of the routes correspond with respective ones of the one or more respective tag fields; and
propagate the one or more respective routes within the provider network based, at least in part, on one or more respective values of the one or more respective tag fields,wherein for a given respective tag field that indicates a local routing scope, the one or more networking devices of the provider network are configured to propagate a respective route that corresponds with the given respective tag field within a limited portion of the provider network that includes the endpoint router, andwherein for another given respective tag field that indicates a larger routing scope, the one or more networking devices of the provider network are configured to propagate the respective route that corresponds with the other given tag field within a larger portion of the provider network that includes the endpoint router.
1 Assignment
0 Petitions
Accused Products
Abstract
A system includes a provider network and a client network connected via a dedicated physical connection. The client network and the provider network exchange routing information using routing protocol messages, such as border gateway protocol (BGP) update messages exchanged during a BGP session. A provider network includes tag field values in outgoing routing protocol messages that indicate a portion of the provider network wherein resources of the provider network associated with a corresponding route are located. The client network may use the tag field value to determine whether to add the route to a routing table of the client network. A client network may also include tag field values in outgoing routing protocol messages to a provider network. The tag field values may indicate what portions of the provider network are to receive the routes from the client network. For example a tag field value may indicate that a route is to be propagated within a limited portion of the provider network.
-
Citations
20 Claims
-
1. A system comprising:
-
a provider network comprising a plurality of physical computing devices configured to implement resources of the provider network; and an endpoint router of the provider network, wherein the endpoint router is connected to a client network of a client of the provider network via a dedicated physical connection between the provider network and the client network, wherein one or more networking devices of the provider network are configured to; receive, via the endpoint router, a routing protocol message from the client network, wherein the routing protocol message comprises; one or more respective routes for devices of the client network; and one or more respective tag fields populated with respective values, wherein respective ones of the routes correspond with respective ones of the one or more respective tag fields; and propagate the one or more respective routes within the provider network based, at least in part, on one or more respective values of the one or more respective tag fields, wherein for a given respective tag field that indicates a local routing scope, the one or more networking devices of the provider network are configured to propagate a respective route that corresponds with the given respective tag field within a limited portion of the provider network that includes the endpoint router, and wherein for another given respective tag field that indicates a larger routing scope, the one or more networking devices of the provider network are configured to propagate the respective route that corresponds with the other given tag field within a larger portion of the provider network that includes the endpoint router. - View Dependent Claims (2, 3, 4, 5)
-
-
6. A method comprising:
-
receiving, at an endpoint router of a provider network that is connected to a client network via a dedicated physical connection between the provider network and the client network, one or more routes for resources of the provider network configured to be provisioned to clients of the provider network as compute resources or storage resources; determining according to a route tagging schema published by the provider network, based on an origin of the one or more routes and a location of the endpoint router in the provider network, one or more respective corresponding tag field values for the one or more routes; and providing to the client network, via the endpoint router, a routing protocol message, wherein the routing protocol message comprises; the one or more routes; and the one or more determined respective tag field values indicating one or more respective portions of the provider network where the resources that correspond with the one or more routes are located. - View Dependent Claims (7, 8, 9, 10, 11, 12, 13, 14)
-
-
15. A non-transitory computer-accessible storage medium storing program instructions that when executed on one or more processors:
in response to receiving, at a provider network, a routing protocol message from a client network of a client of the provider network, wherein the client network is connected to the provider network via a dedicated physical connection, wherein the routing protocol message comprises one or more routes for resources of the client network and one or more respective tag field values that correspond with the one or more routes; propagate the one or more routes within the provider network based, at least in part, on the one or more respective tag field values, wherein in response to a given tag field value indicating a particular value in accordance with a route tagging schema published by the provider network, a given corresponding route is propagated within a limited portion of the provider network; and wherein in response to the given tag field value indicating another value in accordance with the route tagging schema, the given corresponding respective route is propagated within a larger portion of the provider network. - View Dependent Claims (16, 17, 18, 19, 20)
Specification