AWS VPC CIDR in both 10 0 0 0 8 and 192 168 0 0 16 closed

0 votes

I have VPC A with CIDR 10.A.0.0/16 and VPC B with CIDR 10.B.0.0/16. I have VPC A and B peered and updated the route tables and from a server in 10.B.0.0/16 can ping a server in 10.A.0.0/16 and vice versa.

The applications on VPC A also use some IPs in the 192.168.0.0/16 range. Not something I can easily change, but I need to be able to reach 192.168.0.0/16 on VPC A from VPC B.

I've tried adding 192.168.0.0/16 to the route table used for VPC B and setting the target of the peered connection. That does not work, I believe because 192.168.0.0/16 is not in the CIDR block for VPC A.

I'm unable to add 192.168.0.0/16 as a secondary CIDR in VPC A because it is restricted. See CIDR block association restrictions and related question. I understand it is restricted, but why is it restricted? RFC1918 doesn't seem to say anything against using more than one of the private address spaces.

Mar 15 in Others by Edureka
• 13,640 points
341 views

1 answer to this question.

0 votes
The Amazon Virtual Private Cloud (Amazon VPC) allows you to launch AWS resources into a custom virtual network. This virtual network closely matches a typical network you'd run in your own data centre, but with the added benefit of AWS's scalable infrastructure.

VPC ideas on Amazon

The networking layer of Amazon EC2 is called Amazon VPC. See What is Amazon EC2? if you're unfamiliar with the service. To gain a quick introduction, look through the Amazon EC2 User Guide for Linux Instances.

VPCs are defined by the following key concepts:

A virtual private cloud (VPC) is a specialised virtual network for your AWS account.

In your VPC, a subnet is a set of IP addresses.

Classless Inter-Domain Routing (CIDR) is a block in the CIDR protocol. A mechanism for allocating IP addresses and aggregating routes over the internet

A route table is a set of rules for determining where network traffic should be directed.

DHCP options sets: When EC2 instances are launched into VPC subnets, they receive configuration information (such as domain name and domain name server).

Internet gateway – A gateway that connects your VPC to the internet, allowing communication between your VPC's resources and the internet.

Egress-only internet gateways allow an EC2 instance in a subnet to access the internet but restrict internet resources from initiating communication with the instance.

VPC endpoint — Allows you to connect your VPC to AWS services and VPC endpoint services powered by PrivateLink without the use of an internet gateway, NAT device, VPN connection, or AWS Direct Connect connection. To communicate with resources in the service, instances in your VPC do not need public IP addresses.

A managed AWS service that allows EC2 instances in private subnets to connect to the internet, other VPCs, or on-premises networks via NAT gateways.

A NAT instance is a public subnet EC2 instance that allows instances in private subnets to access to the internet, other VPCs, or on-premises networks.
answered Mar 21 by gaurav
• 22,040 points

Related Questions In Others

0 votes
0 answers
0 votes
1 answer

How to create subnet inside a VPC in AWS using Terraform?

Hi@akhtar, You need to use aws_subnet resource inside your ...READ MORE

answered Jul 21, 2020 in Others by MD
• 95,380 points
213 views
0 votes
1 answer

Error cannot provide both a color and a decoration in Flutter container.

Hi@akhtar, The color and decoration arguments cannot both be supplied, since it ...READ MORE

answered Jul 29, 2020 in Others by MD
• 95,380 points
2,913 views
0 votes
0 answers
+2 votes
1 answer

Deploy Docker Containers from Docker Cloud

To solve this problem, I followed advice ...READ MORE

answered Sep 3, 2018 in AWS by Priyaj
• 58,100 points
1,847 views
+1 vote
1 answer
0 votes
1 answer
webinar REGISTER FOR FREE WEBINAR X
REGISTER NOW
webinar_success Thank you for registering Join Edureka Meetup community for 100+ Free Webinars each month JOIN MEETUP GROUP