After you configure the workflow in BlueCat Gateway, you can configure CDV to continuously monitor your Amazon Web Services (AWS) environment for changes to VPC networks, subnets, EC2 instances, ELBv2 (load balancers), Route 53, and VPC endpoints.
To enable continuous monitoring, you must fill in the AWS Credentials, Discovery Options, and Visibility Options sections of the workflow. When you click Start Discovery, the configured settings are applied and AWS information is captured for the AWS regions specified in the Visibility Status and Visibility History sections.
Captured visibility information looks something like this:
Visibility is supported for only the following actions for each type of AWS resource:
- VPC
- Creating a new VPC
- Associating a CIDR (IPv4 and IPv6)
- Disassociating a CIDR (IPv4 and IPv6)
- Deleting a VPC
- Subnet
- Creating a new Subnet
- Associating a CIDR (IPv6)
- Disassociating a CIDR (IPv6)
- Deleting a Subnet
- EC2 instance
- Creating a new EC2 instance
- Stopping an EC2 instance
- Starting an EC2 instance
- Terminating an EC2 instance
- ELBv2
- Creating a new load balancer
- Deleting an existing load balancer
- Route 53
- Creating a public or private hosted zone
- Creating a resource record
- Editing an existing resource record
- Associating a VPC
- Disassociating a VCP
- Deleting an existing resource record
- Deleting an existing public or private hosted zone
Note: Cloud Discovery & Visibility Route 53 does not support visibility for the following records:- Records where the type is edited
- AWS alias records
- VPC Endpoint
- Creating a VPC endpoint
- Deleting a VPC endpoint
- Associating a CIDR (IPv4) to a VPC endpoint
- Disassociating a CIDR (IPv4) from a VPC endpoint
- Associating a security group to a VPC endpoint
- Disassociating a security group from a VPC endpoint
- Elastic Kubernetes Service
- Creating a Cluster
- Deleting a Cluster
- Creating a Node Group
- Deleting a Node Group
- Updating scaling of a Node Group