Amazon AWS - ECS pattern do not collect VM State or checking if VM actually deleted and this can cause discrepancy between install_status and state valuesDescriptionYou might encounter situation where VM Instance CIs t have discrepancy on the status fields as follow: state = Terminated & install_status = InstalledThis can happen when you configured AWS event-driven discovery (https://docs.servicenow.com/bundle/xanadu-it-operations-management/page/product/it-operations-management/task/aws-config-service-cloud-mgt.html) in combination with AWS cloud discovery.Scenario:1) VM got deleted due to AWS notification event. Event processing would mark state = Terminated & install_status = Retired.2) If AWS cloud discovery schedule run not long after, VM got re-installed/recovered by Amazon AWS - ECS pattern. This pattern only update the install_status and not the state.3) Normally, in discovery schedule, Virtual Server (LP) pattern, should be able to find the same VM and properly update with state. So, it won't matter if Amazon AWS - ECS pattern did not update the "state". However, due to "delay" in AWS, even though the VM has been deleted, it might still available on DescribeContainerInstances ECS API response. This VM actually should be deleted, not recovered by Amazon AWS - ECS pattern.Steps to Reproduce 1) Configure AWS event-driven discovery (https://docs.servicenow.com/bundle/xanadu-it-operations-management/page/product/it-operations-management/task/aws-config-service-cloud-mgt.html) 2) Set-up a VM instance as part of ECS cluster in AWS.3) Delete above VM Instance in AWS --- which should trigger delete event and ServiceNow would mark this VM as state = Terminated & install_status = Retired.4) Immediately run cloud discovery schedule for the account that own the VM above.5) Amazon AWS - ECS pattern would update the install_status = Installed , but state is left as Terminated.6) Virtual Server (LP) pattern triggered at the end of discovery would not collect the VM as it is already deleted on AWS.WorkaroundWorkaround: Download Update set Here Remote Update Set Apply this update and run the discovery Related Problem: PRB1793487