The Discovery Options section of the Amazon Web Services (AWS) Setup page lets you configure the information imported from the AWS infrastructure.
If you update the name of a Configuration or View in Address Manager after you enable Discovery and Visibility, Cloud Discovery & Visibility AWS will no longer import AWS infrastructure changes into Address Manager.
When configuring Cloud Discovery & Visibility AWS to discover resources in an AWS GovCloud environment, note that AWS GovCloud does not use external Route 53 zones. To include Route 53 zones as part of a Discovery job, you must first link them to a non-AWS GovCloud account that points to those Route 53 zones. For more information, see https://docs.aws.amazon.com/govcloud-us/latest/UserGuide/setting-up-route53.html.
If you enter the name of an existing Address Manager configuration in the BlueCat Configuration field of the Configuration Options section, CDV automatically populates all views within the Discovery Options section with appropriate values.
When configuring new view names in the relevant view fields, click Create <view name> from the dropdown menu, or press Enter to confirm your selection.
Discover AWS resources options
| Field/Option | Description |
|---|---|
| AWS Private VPC/Subnet | Select this checkbox to import all AWS VPC and Subnet network information. Within Address Manager, private VPCs/Subnets are converted into IPv4 and IPv6 blocks and networks. |
| AWS Public IP Ranges |
Select this checkbox to imports the AWS public address space
information of virtual machines and load balancers within the
region. Within Address Manager, public VPCs are converted into IPv4
and IPv6 blocks and networks.
Note: When this option is unchecked,
the virtual machine and load balancer information is still
imported into Address Manager; however, the IP
ADDRESSES of Public virtual machine and
load balancer devices within Address Manager will be
blank.
|
| AWS VPC
Endpoints Endpoint View |
Select this checkbox to import VPC endpoint information. In Address Manager, the VPC endpoints are converted into the VPC endpoint device type. Also, in Endpoint View, enter the name of the
view that will be created in Address Manager or select an existing
view in Address Manager that will contain the DNS records from the
VPC endpoint.
|
| AWS EC2 Instances |
Select this checkbox to import all EC2 instance information. In Address Manager, the EC2 instances are converted into devices. |
| AWS DNS Hostnames -
Internal DNS Hostname Internal View |
Select this checkbox to import internal DNS record information. The internal DNS records are converted into internal DNS records on Address Manager with the prefix defined in the BlueCat Target Zone field. Also, in DNS Hostname Internal View, enter the
name of the view that will be created in Address Manager, or select
an existing view in Address Manager that will contain the internal
AWS provided name resolution information.
|
| AWS ELBv2 Load Balancers |
Select this checkbox to import all ELBv2 load balancer information. In Address Manager, this is converted into the ELBv2 device type. |
| AWS DNS Hostnames -
External DNS Hostname External View |
Select this checkbox to import external DNS record
information. The external DNS records are converted into external DNS
records on Address Manager with the prefix defined in the
BlueCat Target Zone field. Also, in
DNS Hostname External View, enter the
name of the view that will be created in Address Manager or select
an existing view in Address Manager that will contain the external
AWS provided name resolution information.
|
| AWS Route 53 DNS -
Private DNS Resource Record Private View |
Select this checkbox to import all private AWS Route 53 DNS zone record information. Within Address Manager, the DNS zone records are converted into private DNS records. Also, in DNS Resource Record Private View, enter the name of the view that will be created in Address Manager, or select an existing view in Address Manager that will contain the internal AWS provided name resolution information.
|
| AWS Route 53 DNS -
Public DNS Resource Record Public View |
Select this checkbox to import all public AWS Route 53 DNS zone record information. The DNS zone records are converted into public DNS records on Address Manager. In DNS Resource Record Public View, enter the name of the view that will be created in Address Manager or select an existing view in Address Manager that will contain the external AWS provided name resolution information.
|
| AWS Elastic Network Interface Allocations | Select this checkbox to import all Elastic Network Interface (ENI) information in the region during discovery jobs. ENIs are imported as devices in Address Manager. |
| Ignore Default VPCs |
When checked, the default VPC and its related resources (virtual machines, load balancers, private endpoints, elastic kubernetes, and private DNS zones) will not be added to the BAM configuration during Discovery or Visibiltity jobs. |
| Create Stand-alone PTR Records |
(This setting is available only when AWS DNS Hostnames - Internal is checked and either AWS EC2 Instances or AWS ELBv2 Load Balancers is checked.) If checked, when a host record is created, the corresponding PTR record is also created. These PTR records will be located in external hosts under the internal view. This setting applies to both Discovery and Visibility jobs. |
AWS Elastic Kubernetes Service options
| Field/Option | Description |
|---|---|
| AWS Elastic Kubernetes Service | Select this checkbox to import AWS Elastic Kubernetes Service (EKS) resources, including cluster and node groups. Within Address Manager, clusters are converted into devices and node groups are converted into tags. |
| AWS Internal Resources within Kubernetes Engine |
Select this checkbox to also discover Kubernetes pods and services within EKS resources. CDV will also create a new Configuration for each Kubernetes cluster to hold that cluster's pods and services. Note: CDV does not directly support EKS discovery for Private EKS
Clusters (when the Cluster endpoint access is private). Howver,
it is possible for CDV to access the private endpoints via SSM
Port Forwarding. For more details, see Amazon EKS cluster endpoint
access control on the AWS Documentation
website.
|
| Kubernetes View | Select the Address Manager View that will contain the discovered EKS resources. To use the default View name, select AWS Kubernetes View. |
BlueCat Target Zone options
| Field/Option | Description |
|---|---|
|
Target Zone for Private Endpoints Auto Create Zones for Private Endpoints |
In Target Zone for Private Endpoints, enter the name of the DNS zone on BAM that will contain resource records from private endpoints. CDV will create a zone in BAM based on the entered zone name. Select the Auto Create Zones for Private Endpoints checkbox to create separate subzones for each private endpoint region under the specified Target Zone for Private Endpoints. If cleared, information will be stored in a single zone. |
|
Target Zone for EC2 instances and Load Balancers Auto Create Zones for EC2 instancers and Load Balancers |
In Target Zone for EC2 instances and Load Balancers, enter the name of the DNS zone on BAM that will contain EC2 instance DNS records. Select the Auto Create Zones for EC2 instancers and Load Balancers checkbox to embed AWS availability zones for EC2 Instances and AWS region names for ELBv2 into the provided name resolution. Clear the checkbox otherwise. Note:
In GCP infrastructures, only the Published service type has a region assigned to its private endpoint. When this option is used, CDV will generate a subzone with their region as a name. If the Private Service Conect (PSC) and Virtual Private Service
Connect (VPSC) were not assigned a region, CDV will generate a
subzone named |
| Dynamic Update of DNS Resource Records |
This option is available only when connecting to Address Manager v9.4.0 or later. Select this checkbox to update the DNS records in Address Manager and automatically deploy the changes to the primary BDDS of that zone using selective deployment. This checkbox is disabled by default and only available if you select the Enable Visibility after Discovery checkbox. Attention: You must perform a full DNS deployment to the
managed BDDS before any subsequent selective deployments can be
performed.
If you are configuring the managed BDDS to exclusively manage the cloud infrastructure, you can run a Discovery job to import the cloud infrastructure into your Address Manager. After the view and zone information are successfully imported into Address Manager, you can configure primary and secondary DNS roles for the selected managed BDDS and perform a full DNS deployment. Then, after DNS data is deployed to the managed BDDS, you can enable the Visibility job to continuously monitor changes to your cloud DNS infrastructure and selectively deploy those changes to the managed BDDS. |
Other options
| Field/Option | Description |
|---|---|
| Remove Deleted Resources (Tag Deleted Views/Zones during Rediscovery) |
Select this checkbox to automatically delete resources (except for DNS Views and Zones) that currently exist in Address Manager, but were not found upon rediscovery. Missing View and Zone resources will be tagged for manual inspection and removal. For more details on viewing and manually deleting these tagged resources, see Deleting resources flagged as missing during rediscovery. |
| Dynamic Update of DNS Resource Records |
This option is available only when connecting to Address Manager v9.4.0 or later. Select this checkbox to update the DNS records in Address Manager and automatically deploy the changes to the primary BDDS of that zone using selective deployment. This checkbox is disabled by default and only available if you select the Enable Visibility after Discovery checkbox. Attention: You must perform a full DNS deployment to the
managed BDDS before any subsequent selective deployments can be
performed.
If you are configuring the managed BDDS to exclusively manage the cloud infrastructure, you can run a Discovery job to import the cloud infrastructure into your Address Manager. After the view and zone information are successfully imported into Address Manager, you can configure primary and secondary DNS roles for the selected managed BDDS and perform a full DNS deployment. Then, after DNS data is deployed to the managed BDDS, you can enable the Visibility job to continuously monitor changes to your cloud DNS infrastructure and selectively deploy those changes to the managed BDDS. |