Rediscovery occurs when you rerun the same discoveries to update, delete, and import new cloud resources based on discovery tasks you ran before. This is useful when technical or security restrictions prevent you from running visibilty tasks on your cloud infrastructure.
For more details on setting up your system to support rediscovery, see Rediscovery of cloud resources.
Only certain actions are tracked by AWS rediscovery. These actions are as follows:
- VPC/Subnets
- Creating a new VPC/Subnet
- Updating a CIDR of a VPC/Subnet
- Deleting a VPC/Subnet
- EC2 instances
- Creating a new EC2 instance
- Updating an EC2 instance state
- Deleting an EC2 instance
- Load balancers
- Creating a new load balancer
- Deleting a load balancer
- Route 53
- Creating a new hosted zone
- Creating a new record
- Deleting a hosted zone
- Deleting a record
- VPC Endpoints
- Creating a new VPC endpoint
- Deleting a VPC endpoint
- Updating a CIDR (IPv4) for a VPC endpoint
- Updating a security group for 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
- Elastic Network Interface (ENI)
- Creating an ENI
- Deleting an ENI
- Attaching an ENI to an EC2 instance
- Detaching an ENI from an EC2 instance or EKS cluster
- Assigning or unassigning one or more IPv4/IPv6 addresses, an IPv4 prefix, or IPv6 prefix delegations from a network interface
Attention:
- Selective Deployment of changes is not supported for rediscovery.
- If the name or value of a Cloud DNS record is changed, upon rediscovery, the record will be deleted and reimported into Address Manager as a new record.