I have multiple VPC in my account and I created most of VPC using subnet 10.0.0.0/8 or 192.168.0.0/16 or 172.16.0.0/12 subnet blocks.
I am exhausted with my range due to not optimizing the IP address properly and adding a wrong route of 10.0.0.0/8 under a VPC. I got to know about this when I tried attempted to establish VPC peering between two different VPC of 10.0.0.0 subnet. I got to know later that I can use CIDR range 20.0.0.0/16 and 30.0.0.0/16 as private address in aws to create VPC. Also I created a VPC with CIDR 20.0.0.0/16 and it works.
How come aws can offer multiple IP range for private IP address to create VPC and multiple subnet under VPC? Can somebody help me to understand aws private IP range?
Is this something being virtual we can use any range of IP address as private address? How does this not affect connectivity from aws server to internet if we can choose any random CIDR as private IP address or there is some limit?
Answer
Attribution
Source : Link , Question Author : Pratap , Answer Author : Community
