AWS Application and Network Cloud load balancer records are updated instead creating new CI, if LB record with the same Name is created into the AWS console and the previous is deleted - Known Error

AWS Application and Network Cloud load balancer records are updated instead creating new CI, if LB record with the same Name is created into the AWS console and the previous is deleted Description AWS Cloud load balancer records are being overwritten because object_id is being copied over from name and at times we might create a load balancer with the same name. So we might need to change the OOB identifier so that the old record always gets updated leaving all the decommissioned history associated with it.

If a CI record from type Application or Network Cloud load balancer with example name "Testload" is deleted and CI with the same name is created into the AWS console, the discovery will update the same record into the CMDB instead of mark the same as absent and create a new one. This is happening due to the reason 'object_id' is the identifier for class 'cmdb_ci_cloud_load_balancer' where the Name of the Application or Network Cloud load balancer is serving as 'object_id'.

Steps to Reproduce

1. As per AWS discovery, let's create a AWS Cloud load balancer with name as "Testload" (for example) 2. Delete or decommission this previously created network or application cloud load balancer from the AWS console. 3. Now create a new AWS Cloud load balancer with same name as "Testload" from the AWS console. 4. Re-run the discovery and now discovery will update the old record and so all the old data will still be associated to this new AWS Cloud load balancer on CMDB.

Workaround All the changes applied to the following discovery patterns:

1. Amazon AWS - Application and Network LB (LP) - where changes for the identification of the main CI 'cmdb_ci_cloud_load_balancer' were done, changing the object_id to ARN (Amazon resource name). And the rest of the patterns are dependent of this one, by relations or large payload mechanism discovery context ( source_native_key ).

2. Amazon AWS - LB Pool (LP)

3. Amazon AWS - LB Service (LP)

4. Amazon AWS - NIC (LP)

The changes are only applicable for AWS Cloud Load balancers of type 'Application' or 'Network'. The changes are not applicable for AWS Cloud Load balancers of type 'Classic' due to the fact, for the current moment the vendor (AWS) don't provide ARNs (Amazon Resource Names) for Load Balancer of type classic, which are discovered via REST API version 1. The main changes upon the pattern mentioned above are that the identifier of the Cloud Load balancer CI is changed from Name to ARN (Amazon resource name).

Example Name format: lb-for-vpc-link

Example ARN format: arn:aws:elasticloadbalancing:us-east-1:012345678912:loadbalancer/net/lb-for-vpc-link/63ffb32863c12bf4

The official AWS documentation we have two version of APIs 2012 (Classic LB infrastructure) and 2015 (Network and Application LB Infrastructure) and both of the APIs returns different data.

Link to the official documentation by vendor:

https://docs.aws.amazon.com/elasticloadbalancing/

Elastic Load Balancing - Version 1 (Classic Cloud Load Balancers)

https://docs.aws.amazon.com/elasticloadbalancing/2012-06-01/APIReference/Welcome.html

Elastic Load Balancing - Version 2 (Network and Application Cloud Balancers )

https://docs.aws.amazon.com/elasticloadbalancing/latest/APIReference/Welcome.html

The changes will be part of plugin ' Discovery and Service Mapping Patterns ' ( sn_itom_pattern ) version 1.0.87