# US 2018/0324085 A1 · Interfaces to manage inter-region connectivity for direct network peerings > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 2018/0324085 A1 - Document ID: US20180324085A1 - Status: Published application - Kind: A1 - Application number: 16/024,549 - Filed: 2018-06-29 - Published: 2018-11-08 - Earliest claimed: 2011-12-22 - Assignees: Amazon Technologies, Inc. - Applicants: Amazon Technologies, Inc. - Inventors: Andrew J. Doane; Kevin Christopher Miller; David B. Lennon - Web page: https://patentgrep.com/patent/US20180324085A1 ## CPC - H04L 45/306: {Route determination based on the nature of the carried application} - H04L 45/00: Routing or path finding of packets in data switching networks (routing or path finding in wireless networks H04W40/00) - H04L 45/02: Topology update or discovery - H04L 45/42: Centralised routing - H04L 45/033: by updating distance vector protocols - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) ## Abstract Methods and apparatus for interfaces to manage inter-regional connectivity for direct network peerings. A system may include a connectivity coordinator, a first resource collection in a first geographical zone and a second resource collection in a second geographical zone. The coordinator implements a programmatic interface defining connectivity operations. The coordinator receives a request via the interface to establish a logically isolated network path to the second resource collection on behalf of a client that has a dedicated physical link set up to connect to the first resource collection. In response to the request, the coordinator performs one or more configuration operations to enable traffic to flow from the client's network to the second resource collection over a logically isolated network path using the dedicated physical link. ## Claims ### Claim at position 1 -22. (canceled) ### Claim 23 A system, comprising: a plurality of resource collections of a provider network, including a first resource collection and a second resource collection, wherein the first and second resource collections each comprise compute or storage resources configured to provide compute or storage services to clients of the provider network, and wherein the first resource collection is in a different geographical zone of the provider network than the second resource collection; an endpoint router associated with the first resource collection, wherein the endpoint router links the first resource collection to a client network of a client via a dedicated physical network link between the provider network and the client network; and a connectivity coordinator configured to: receive a connectivity request from the client to establish a network path from the client network to the second resource collection; and perform one or more configuration operations to enable traffic to flow from the client network to the second resource collection, wherein the traffic flows over the dedicated physical network link between the client network and the first resource collection of the provider network and through the provider network to the second resource collection. ### Claim 24 (depends on 23) The system of claim 23, wherein the compute or storage resources of the first resource collection are included in a first data center located in a first geographical zone of the provider network, and wherein the compute or storage resources of the second resource collection are included in a second data center located in a second geographical zone of the provider network. ### Claim 25 (depends on 24) The system of claim 24, wherein the first data center located in the first geographical zone and the second data center located in the second geographical zone are connected via a dedicated network path of the provider network between the first data center and the second data center, wherein the one or more configuration operations cause traffic to flow from the client network to the first data center over the dedicated physical network link and through the provider network to the second resource collection over the dedicated network path between the first data center and the second data center. ### Claim 26 (depends on 25) The system of claim 25, wherein the data center in the first geographical zone, the data center in the second geographical zone, and the dedicated network path are managed by an operator of the provider network. ### Claim 27 (depends on 23) The system of claim 23, wherein the first resource collection is located local to the client network and the second resource collection is located remote from the client network. ### Claim 28 (depends on 23) The system of claim 23, wherein the first resource collection is local to a first portion of the client network, and the second resource collection is local to a second portion of the client network, and wherein the one or more configuration operations cause traffic to flow between the second resource collection and the second portion of the client network over the dedicated physical network link linking the first portion of the client network to the first resource collection. ### Claim 29 (depends on 23) The system of claim 23, wherein the connectivity coordinator is further configured to: transmit connectivity metadata and instructions to a client device in the client network, via a path other than the dedicated physical network link, wherein the instructions comprise instructions to transmit the connectivity metadata to a metadata target at the second resource collection of the provider network, wherein the connectivity coordinator performs the one or more configuration operations to enable traffic to flow from the client network to the second resource collection over the dedicated physical network link in response to validating the connectivity metadata when sent from the client network and received at the second resource collection. ### Claim 30 (depends on 23) The system of claim 23, wherein the connectivity coordinator is further configured to: receive a remote resource collection enumeration request; and provide a response comprising a list of other remote resource collections to which a logically-isolated network path can be established over the dedicated physical network link. ### Claim 31 A method, comprising: presenting a connectivity service to a client of a provider network, wherein the provider network comprises a first resource collection and a second resource collection located in different geographic locations, wherein the first and second resource collections each comprise compute or storage resources configured to provide compute or storage services to the client of the provider network; receiving a connectivity request from the client to establish a logically isolated network path to the second resource collection using a dedicated physical link established between an endpoint router associated with the first resource collection and a client network of the client; and performing a configuration operation to enable traffic to flow from the client network to the second resource collection over the dedicated physical link between the client network and the first resource collection and through the provider network to the second resource collection. ### Claim 32 (depends on 31) The method of claim 31, further comprising: in response to receiving the connectivity request, sending instructions to the client to transmit connectivity metadata to a destination address within the provider network; and prior to performing the configuration operation, verifying that the connectivity metadata was transmitted in accordance with the instructions. ### Claim 33 (depends on 32) The method as recited in claim 32, wherein the connectivity metadata is encoded in accordance with an encryption algorithm set up to secure communication between the connectivity coordinator and a network device associated with the destination address. ### Claim 34 (depends on 33) The method of claim 33, wherein the instructions are sent via a public network link to a portion of the client network that is local to the second resource collection. ### Claim 35 (depends on 34) The method of claim 34, wherein performing the configuration operation causes traffic to flow between the second resource collection and the portion of the client network local to the second resource collection via the dedicated physical network link between the client network and the first resource collection. ### Claim 36 (depends on 31) The method of claim 31, wherein the connectivity service includes a connectivity coordinator implementing a programmatic interface defining connectivity operations available to the client, wherein the interface comprises one or more of: an application programming interface, a command line interface, a graphical user interface or a web interface. ### Claim 37 (depends on 31) The method of claim 31, wherein the compute or storage resources of the first resource collection are included in a first data center located in a first geographical zone of the provider network, and wherein the compute or storage resources of the second resource collection are included in a second data center located in a second geographical zone of the provider network, wherein a dedicated network path of the provider network connects the first data center and the second data center. ### Claim 38 One or more non-transitory computer-accessible storage media storing program instructions that when executed on or across one or more processors: implement a programmatic interface defining connectivity operations available to a client of a provider network, wherein the provider network comprises a plurality of resource collections each comprising compute or storage resources configured to provide compute or storage services to clients of the provider network, and wherein the compute or storage resources of a first resource collection of the provider network are located in a different geographical location than the compute or storage resources of a second resource collection of the provider network; receive a connectivity request from the client to establish a logically isolated network path from the client network to the second resource collection; and perform one or more configuration operations to enable traffic to flow from the client network to the second resource collection over a dedicated physical network link between the client network and the first resource collection of the provider network and through the provider network to the second resource collection. ### Claim 39 (depends on 38) The one or more non-transitory computer-accessible storage media as recited in claim 38, wherein the instructions when executed on or across the one or more processors: send, in response to receiving the connectivity request, instructions to the client to transmit connectivity metadata to a destination address within the provider network; and verify, prior to performing the configuration operation, that the connectivity metadata was transmitted in accordance with the instructions. ### Claim 40 (depends on 38) The one or more non-transitory computer-accessible storage media as recited in claim 38, wherein the instructions when executed on or across the one or more processors: provide, in response to receiving an enumeration request, a list of remote resource collections for which a logically-isolated network path can be established between the client network and the provider network over the dedicated physical network link between the client network and the first resource collection of the provider network. ### Claim 41 (depends on 38) The one or more non-transitory computer-accessible storage media as recited in claim 38, wherein: the connectivity request specifies one or more characteristics of the logically isolated network path to be established from the client network to the second resource collection; and the one or more configuration operations establish the logically isolated network path in accordance with the characteristics specified in the connectivity request. ### Claim 42 (depends on 38) The one or more non-transitory computer-accessible storage media as recited in claim 38, wherein: the connectivity request includes an identifier for the dedicated physical network link between the provider network and the client network to be used to establish the logically isolated network path; and the one or more configuration operations establish the logically isolated network path via the dedicated physical network link identified in the connectivity request.