User Tools

Site Tools


wiki:aws_vpc_peering

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

wiki:aws_vpc_peering [2025/03/05 12:12] – created antisawiki:aws_vpc_peering [2025/03/07 09:09] (current) – [aws vpc peering] add screenshots and more info antisa
Line 5: Line 5:
  
   * Create the peering connection between the 2 subnets   * Create the peering connection between the 2 subnets
 +You shouldn't need any special DNS settings to resolve DNS A records in the other vpc, default settings should be ok when creating the peering connection:
 +{{ :wiki:screenshots:2025:aws-peer-conn-dns.png?600 |}}
 +
   * Create the routes in both VPCs for the respective subnets with the peering connection as a gateway   * Create the routes in both VPCs for the respective subnets with the peering connection as a gateway
 +The routes should be created in the appropriate route table of the subnets, because you may have a default main route table ("rtb-xxx..." below) and a custom route table ("eks-route-table" below) for which you associated the subnets, so you need to create the routes for the custom table 
 +{{ :wiki:screenshots:2025:eks-resource-map-route.png?600 |}}
   * Make sure the security groups allow traffic from one subnet to the other   * Make sure the security groups allow traffic from one subnet to the other
  
Line 13: Line 18:
  
 The address 10.10.10.15 is some resource in the second VPC. The address 10.10.10.15 is some resource in the second VPC.
 +
 +
 +
 ====== Tested on ====== ====== Tested on ======
  
wiki/aws_vpc_peering.txt · Last modified: 2025/03/07 09:09 by antisa

Except where otherwise noted, content on this wiki is licensed under the following license: CC0 1.0 Universal
CC0 1.0 Universal Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki