Some of the AWS VM instances CIs are not getting discovered for the sub accounts

Abhishek41
Tera Contributor

Hi All,

We have configured AWS credentialess assume role-based discovery in our environment using the master account.

We are able to discover the VM instances for the AWS sub accounts but when we started validating with the AWS cloud team, we find that the VM instance count is much less as compared to ServiceNow under VM instance table VS AWS cloud console. we checked all the configuration for AWS discovery, but all looks fine as some of the VM instances are already being discovered under the all sub-accounts. 

Can someone help me what could be the reason why all VM instances are not getting discovered (cloud-based discovery) so that we can troubleshoot accordingly. 

 

Thanks,

Abhishek

3 REPLIES 3

pratiksha5
Mega Sage

Check this series. It helped me: https://www.youtube.com/watch?v=Rdn9DypfTTc

In this Share the Wealth session, Senior Technical Consultant Emily Hattier and Architect Scott Murphy provide an overview of AWS Cloud Discovery and will walk us through AWS MID server and AWS Discovery Setup. Amazon AWS Cloud Discovery for ServiceNow Utha. Use Cloud Discovery to discover virtual

Abhishek41
Tera Contributor

Hi @pratiksha5

I have checked the video configuration wise we are good we were getting some VM instance discovered previously but suddenly we stopped seeing them . When I tried debugging the VM host pattern logs I am seeing the error saying " Host is empty Failed Condition(s): [(${all_hosts} : value=[]) IS NOT EMPTY ]" . Do you know why we are getting for the cloud vm instance discovery ?

Any inputs will be appriciated.

Thanks,

Abby

Abhishek

We are getting the same error. DId you get this resolved?