<div dir="ltr" style="text-align: left;">This section demonstrates the configuration for VPC peering connections in which you configure your route tables to access to the entire CIDR block of the peer VPC. For more information about scenarios in which you might need a specific VPC peering connection configuration, </p>
<div>
<div>
<div>
<div>
<h2 style="clear: both;">Two VPCs Peered Together</h2>
</div>
</div>
</div>
<p>You have a VPC peering connection (<code>pcx-11112222</code>) between VPC A and VPC B, which are in the same AWS account, and do not have overlapping CIDR blocks.</p>
<div>
<div></div>
</div>
<p>You may want to use this kind of configuration when you have a two VPCs that require access to each others&#8217; resources. For example, you set up VPC A for your accounting records, and VPC B for your financial records, and now you want each VPC to be able to access each others&#8217; resources without restriction.<br />The route tables for each VPC point to the relevant VPC peering connection to access the entire CIDR block of the peer VPC.</p>
<div>
<div>
<table border="0" cellspacing="0">
<colgroup>
<col></col>
<col></col>
<col></col>
</colgroup>
<thead>
<tr>
<th>Route Table</th>
<th>Destination</th>
<th>Target</th>
</tr>
</thead>
<tbody>
<tr>
<td rowspan="2">VPC A</td>
<td>172.16.0.0/16</td>
<td>Local</td>
</tr>
<tr>
<td>10.0.0.0/16</td>
<td>pcx-11112222</td>
</tr>
<tr>
<td rowspan="2">VPC B</td>
<td>10.0.0.0/16</td>
<td>Local</td>
</tr>
<tr>
<td>172.16.0.0/16</td>
<td>pcx-11112222</td>
</tr>
</tbody>
</table>
</div>
</div>
</div>
<div>
<div>
<div>
<div>
<h2 style="clear: both;">One VPC Peered with Two VPCs</h2>
</div>
</div>
</div>
<p>You have a central VPC (VPC A), and you have a VPC peering connection between VPC A and VPC B (<code>pcx-12121212</code>), and between VPC A and VPC C (<code>pcx-23232323</code>). The VPCs are in the same AWS account, and do not have overlapping CIDR blocks. </p>
<div>
<div></div>
<div></div>
</div>
<p>You may want to use this &#8216;flying V&#8217; configuration when you have resources on a central VPC, such as a repository of services, that other VPCs need to access. The other VPCs do not need access to each others&#8217; resources; they only need access to resources on the central VPC.</p>
<div>
<div>Note</div>
<p>VPC B and VPC C cannot send traffic directly to each other through VPC A. VPC peering does not support transitive peering relationships, nor edge to edge routing. You must create a VPC peering connection between VPC B and VPC C in order to route traffic directly between them. For more information,</p></div>
<p>The route tables for each VPC point to the relevant VPC peering connection to access the entire CIDR block of the peer VPC. </p>
<div>
<div>
<table border="0" cellspacing="0">
<colgroup>
<col></col>
<col></col>
<col></col>
</colgroup>
<thead>
<tr>
<th>Route Table</th>
<th>Destination</th>
<th>Target</th>
</tr>
</thead>
<tbody>
<tr>
<td rowspan="3">VPC A</td>
<td>172.16.0.0/16</td>
<td>Local</td>
</tr>
<tr>
<td>10.0.0.0/16</td>
<td>pcx-12121212</td>
</tr>
<tr>
<td>192.168.0.0/16</td>
<td>pcx-23232323</td>
</tr>
<tr>
<td rowspan="2">VPC B</td>
<td>10.0.0.0/16</td>
<td>Local</td>
</tr>
<tr>
<td>172.16.0.0/16</td>
<td>pcx-12121212</td>
</tr>
<tr>
<td rowspan="2">VPC C</td>
<td>192.168.0.0/16</td>
<td>Local</td>
</tr>
<tr>
<td>172.16.0.0/16</td>
<td>pcx-23232323</td>
</tr>
</tbody>
</table>
</div>
</div>
</div>
<div>
<div>
<div>
<div>
<h2 style="clear: both;">Three VPCs Peered Together</h2>
</div>
</div>
</div>
<p>You have peered three VPCs together in a full mesh configuration. The VPCs are in the same AWS account and do not have overlapping CIDR blocks:</p>
<div>
<ul type="disc">
<li>VPC A is peered to VPC B through VPC peering connection <code>pcx-aaaabbbb</code></li>
<li>VPC A is peered to VPC C through VPC peering connection <code>pcx-aaaacccc</code></li>
<li>VPC B is peered to VPC C through VPC peering connection <code>pcx-bbbbcccc</code></li>
</ul>
</div>
<div>
<div></div>
<div></div>
</div>
<p>You may want to use this full mesh configuration when you have separate VPCs that need to share resources with each other without restriction; for example, as a file sharing system.<br />The route tables for each VPC point to the relevant VPC peering connection to access the entire CIDR block of the peer VPCs. </p>
<div>
<div>
<table border="0" cellspacing="0">
<colgroup>
<col></col>
<col></col>
<col></col>
</colgroup>
<thead>
<tr>
<th>Route Tables</th>
<th>Destination</th>
<th>Target</th>
</tr>
</thead>
<tbody>
<tr>
<td rowspan="3">VPC A</td>
<td>172.16.0.0/16</td>
<td>Local</td>
</tr>
<tr>
<td>10.0.0.0/16</td>
<td>pcx-aaaabbbb</td>
</tr>
<tr>
<td>192.168.0.0/16</td>
<td>pcx-aaaacccc</td>
</tr>
<tr>
<td rowspan="3">VPC B</td>
<td>10.0.0.0/16</td>
<td>Local</td>
</tr>
<tr>
<td>172.16.0.0/16</td>
<td>pcx-aaaabbbb</td>
</tr>
<tr>
<td>192.168.0.0/16</td>
<td>pcx-bbbbcccc</td>
</tr>
<tr>
<td rowspan="3">VPC C</td>
<td>192.168.0.0/16</td>
<td>Local</td>
</tr>
<tr>
<td>172.16.0.0/16</td>
<td>pcx-aaaacccc</td>
</tr>
<tr>
<td>10.0.0.0/16</td>
<td>pcx-bbbbcccc</td>
</tr>
</tbody>
</table>
</div>
</div>
</div>
<div>
<div>
<div>
<h2 style="clear: both;">One VPC Peered with Multiple VPCs</h2>
</div>
</div>
</div>
<p>You have a central VPC (VPC A) that&#8217;s peered to the following VPCs:</p>
<div>
<ul type="disc">
<li>VPC B through <code>pcx-aaaabbbb</code></li>
<li>VPC C through <code>pcx-aaaacccc</code></li>
<li>VPC D through <code>pcx-aaaadddd</code></li>
<li>VPC E through <code>pcx-aaaaeeee</code></li>
<li>VPC F through <code>pcx-aaaaffff</code></li>
<li>VPC G through <code>pcx-aaaagggg</code></li>
</ul>
</div>
<p>VPC A is peered with all other VPCs, but the other VPCs are not peered to each other. The VPCs are in the same AWS account and do not have overlapping CIDR blocks. </p>
<div>Note</div>
<p>None of the other VPCs can send traffic directly to each other through VPC A. VPC peering does not support transitive peering relationships, nor edge to edge routing. You must create a VPC peering connection between the other VPCs in order to route traffic between them. </p></div>

The Cyber Security, Compliance & Cloud
Cyber Security | Digital Transformation | Cloud Computing
