Basic Visibility Options
|Enable Visibility after Discovery||Select this checkbox to continuously monitor changes to the discovered VPC/Subnets, EC2, Route 53 resources, and VPC Endpoints from the AWS infrastructure.|
Address Manager User options
Address Manager Username
Address Manager Password
Enter the username of the Address Manager user.
Note: This user should be an administrative API user with full permissions.Also, in Address Manager Password, enter the password for the Address Manager user.
|Service Account Key||
Enter the AWS access key ID for the account used in the AWS Credentials page.
|Service Account Secret||Enter the AWS secret access key for the account used in the AWS Credentials page.|
Advanced AWS Parameters options
|Enable AWS Role Assumption||Select this checkbox to use AssumeRole security credentials
within your account to gain visibility into your AWS
Attention: If you deployed Cloud Discovery & Visibility on an AWS EC2 Instance, the following fields do not appear if you also selected the Get Credentials from environment checkbox within the AWS Credentials page.
|AWS Role ARN||
Note: This field is not available if you're automatically acquiring Cloud Discovery & Visibility credentials from an EC2 Instance. (That is, if CDV is deployed on an AWS EC2 Instance and you selected the Get Credentials from environment checkbox within the AWS Credentials page.)Enter the AWS role assumption ARN. The AWS role ARN must be in the following format:
|Override Queue and Notification Default Names||
Select the Override Queue and Notification Default Names checkbox to specify custom queue and notification names for retrieving data from your AWS infrastructure. We recommend using this feature only if absolutely necessary, such as when names of resources in your cloud environments must conform to company standards.
Selecting this checkbox displays the following fields:
If you enter a name that already exists in the resource group, you'll be asked if you want to reuse the same name. Click Cancel (and choose a different name) if you think your Visibility jobs will affect other Visibility jobs using the same name. Click Reuse to confirm use of the same name (that is, if you're sure that your jobs will not impact other Visibility jobs with the same name).
Attention: Behavior when overriding queue and notification default names