No overlapping address spaces
In the following image, two Private VPC networks have been created on AWS.
Upon the successful import of the data into Address Manager, the block appear under the IPv4 tab within the IP Space tab in the selected configuration that is generated based on the VPCs created on AWS. The following image displays the data in Address Manager.
By default, AWS provides additional public VPCs that also appear under the IPv4 tab within the IP Space tab if you selected to import the AWS Public IP Ranges from the Discovery Options settings. The following image shows the imported public IP ranges from AWS.
Cloud Discovery & Visibility AWS also imports IPv6 data that appears under the IPv6 tab within the IP Space tab based on the Private VPCs that have been created in the AWS infrastructure. The following image shows imported IPv6 blocks in Address Manager.
Similarly, if you selected to import the AWS Public IP Ranges from the Discovery Options settings, the additional public VPCs provided by AWS are imported into Address Manager as IPv6 blocks.
Overlapping address spaces
In the following image, two private VPCs have been created on AWS where the 10.0.0.0/16 and 10.0.0.0/18 address spaces are overlapping in networks vpc-1 and vpc-2.
Upon the successful import of the data into Address Manager, a two new configuration are created in Address Manager to account for the overlapping address space. Depending on the AWS Route 53 configurations, an additional Route 53 configuration might be created. The following image displays the configurations created in Address Manager.
