Configuring VPC Peering for Web-Servers Connectivity
Question
An IT company has recently acquired another firm in different continents.
Both companies are using AWS cloud infrastructure for their IT infrastructure.
Initially, they want to share web application servers deployed in VPC of each.
As a SysOps administrator of the company, you plan to configure VPC peering between 2 IT firms.
To set up connectivity between Web-servers, how is routing configuration done between peering VPC?
Answers
Explanations
Click on the arrows to vote for the correct answer
A. B. C. D.Correct Answer: C.
To set up VPC peering, the owner of a requestor VPC sends a VPC peering request to acceptor VPC.
Once a peering connection is established, owner of each VPC needs to manually add routes for destination servers in other VPC pointing to target as pcx-11112222.
Option A is incorrect as routes are not automatically added.
The owner of each VPC needs to add routes for peering VPC manually.
Option B is incorrect as the Owner of requestor VPC can perform routing only for VPC he owns.
For peering VPC, routing must be done by the owner of that VPC.Option D is incorrect as Owner of acceptor VPC can perform routing only for VPC he owns.
For more information on routing for VPC peering, refer to the following URL-
https://docs.aws.amazon.com/vpc/latest/peering/vpc-peering-basics.htmlSure, I'll be glad to provide a detailed explanation of how routing configuration is done between peering VPCs.
When two VPCs are peered, they can communicate with each other using private IP addresses. This means that resources in one VPC can access resources in the other VPC over the peering connection, just as if they were in the same VPC.
To set up connectivity between the web-servers in the two VPCs, routing configuration needs to be done. Routing tells the VPC how to route traffic to the destination. When two VPCs are peered, the routing configuration is done in the routing tables of each VPC.
Each VPC has its own routing table that specifies how traffic is routed within the VPC. When VPC peering is established, a route is automatically added to the routing tables of both VPCs for the IP address range of the peered VPC. This route directs traffic destined for the peered VPC to the peering connection.
So, the correct answer is A - "Once VPC peering connection is accepted by the acceptor VPC, routes are automatically added in the routing table for each VPC."
This means that both VPCs will be able to communicate with each other once the VPC peering connection is accepted by the acceptor VPC. The routing will be automatically configured and there is no need for any manual configuration.
It is worth noting that if there are any additional routes required for traffic to flow between the web-servers, such as routes to reach external networks or to route traffic to other subnets within the VPCs, then those routes will need to be manually configured in the routing tables of the respective VPCs. However, for the purpose of communication between the peered VPCs, the routes will be automatically added.
