- Create a new VPC (e.g: cmpe281-kohra (Do not reuse cmpe281 VPC used for course labs) using the wizard as it won't work and might impact the current setup.
Note: The CIDR blocks for each of our VPCs should be unique for peering to work.
Vish is using: 10.2.0.0/16 Arkil is using: 10.3.0.0/16
Would suggest below CIDR blocks for others to make it easier: Saket : 10.4.0.0/16 Varun Jain: 10.5.0.0/16 Varun S: 10.6.0.0/16
- Next, each of us have to create VPC peering connecting with other 4 VPCs (unless there's no need to connect to a specific VPC) per below.
VPC details for creating peering requests:
NOTE : Make sure that the peer vpc is also is the same region, else manually input it. We need 3 parameter to connect VPC Peering
- Account ID
- VPC ID
- Region
| Name | Account ID | VPC ID |
|---|---|---|
| Vish | 466657727551 | vpc-00f6d19f684379e31 |
| Arkil | 678940506936 | vpc-0d37111ce05e78c31 |
| Saket | 892072204237 | vpc-03bb33674b5c9218b |
| Varun J | 771966576901 | vpc-0256cb23f6a42cbe8 |
| Varun S | 874791278795 | vpc-056471c573ce9e107 |
- Once created, an approval request is sent to the accepter who needs to accept it. Once accepted, check the status of VPC peering and it needs to change to "Active".
- Edit the DNS settings under Actions to enable "Requester DNS resolution"
- Edit route tables of public subnet. Add CIDR block of other VPC. For ex Vish CIDR: 10.2.0.0/16 as peering connection
- Edit route tables of private subnet. Add CIDR block of other VPC. For ex Vish CIDR: 10.2.0.0/16 as peering connection
- Subnet associations of public subnet
