Cloud Central

 Hi! This blog is the continuation of part-1, which is about the multi-VPC networking infrastructure. If you have not checked it out, click on the link below  Multi-VPC connectivity, AWS network infrastructure.(Part-1) :  https://cloudcentralblogs.blogspot.com/2022/05/multi-vpc-connectivity-aws-network.html So lets get into it, shall we? VPC to VPC connectivity AWS PrivateLink Source of above picture: AWS documentation This service can be used to route traffic between different VPCs and access AWS services on a private network using VPC endpoint, as shown in the above figure. The consumer and the service are not required to be in the same VPC. If the VPC is different, the consumer and service provider VPCs can have overlapping IP address ranges. So this a good option when client and servers in the two VPCs have overlapping IP addresses, as the endpoint configuration in consumer VPC leads to the creation of an ENI in the subnet with a private IP address that...

  Overview Amazon Web Services (AWS) customers often rely on hundreds of accounts and virtual private clouds (VPCs) to segment their workloads and expand their footprint. When a VPC needs to communicate with another VPC present in the same or different region/account, there should be a connection established. As the number of VPCs inc reases in an account or in a region due to the expansion of workload, the communication between those VPCs and the VPCs present in different accounts or regions becomes cumbersome. There could be various use cases and problems to solve other than mentioned above. AWS provides us choices that we can opt, which best suits our network infrastructure requirements. VPC to VPC connectivity VPC Peering AWS VPC peering is a point-to-point connectivity between VPCs. No transitive connections can be leveraged. Maximum of 125 peering connections per VPC. For hybrid connectivity i.e. peering connection between AWS VPC and on-premises network, VPN or Direct conne...