Merge private account networks through a global router
If your infrastructure is in different accounts, you can federate the private networks of those accounts. A global router is used for aggregation.
Principle of operation
To interconnect private networks, each account must have a global router. Private subnets that need to be accessed from another account are connected to global routers. After unification, the subnets on the routers will be in the same address space, so their addressing should not overlap: the IP addresses of each subnet should not overlap with the IP addresses of other subnets.
On request, we merge global routers and their routing tables. After merging, you can route traffic between all subnets that are connected to the merged routers.
Example of a merger
Need to merge private networks in two accounts:
- account 1 has a private subnet connected to the global router.
192.168.0.0/24
. IP address192.168.0.2
assigned to a dedicated server, IP address192.168.0.1
is assigned as the gateway to the global router; - account 2 has a private subnet connected to the global router
172.16.0.0/24
. IP address172.16.0.2
assigned to the cloud server, IP address172.16.0.1
is assigned as the gateway to the global router; - global routers in the accounts are merged.
In order for servers to exchange traffic, you need:
-
combine global routers;
-
prescribe routes:
- on a dedicated server — up to a cloud server
172.16.0.2
through the gateway192.168.0.1
; - on a cloud server — up to a dedicated server
192.168.0.2
through the gateway172.16.0.1
.
- on a dedicated server — up to a cloud server

