Amazon (AWS) Peering Network

Peering connection Test 1.1 Tokyo account A create a peer connection

Note that the VPC segments on both sides cannot be duplicated, and the routing table cannot be configured if repeated

Enter information for both parties

Account ID and VPC

1.2 Tokyo Account A view

View connection Information

Display is processing accept, requires another account, authorization confirmation

1.3 Singapore Account B view

View the current display

1.4 Singapore Account B Select Accept Request

1.5 Singapore Account B now look at the active state.

1.6 Tokyo Account A view connection status

1.7 Tokyo account A, set up an interoperable subnet

The local VPC is 172.30.0.0/16 (the subnet here is a private subnet)

Each other's VPC is 172.29.0.0/16

The routing table is configured as follows, keeping in mind that security groups are also configured so that they cannot connect and ping

1.8 Singapore Account B, set up an interoperable subnet

Local VPC is 172.29.0.0/16 (local subnet is a public subnet)

Each other's VPC is 172.30.0.0/16

Create a machine Tokyo and Singapore each

2.1 Tokyo View

Tokyo Account A IP 172.30.102.171

Singapore Account B IP172.29.10.159

Network Interoperability

2.2 Singapore View

Tokyo Account A IP 172.30.102.171

Singapore Account B IP172.29.10.159

Network Interoperability

Amazon (AWS) Peering Network