AWS Cloud Discovery : VM instances are not getting discovered

[upasmita]

We are facing issue in Cloud Discovery for AWS with ServiceNow.

1. Created AWS Master accounts and credentials with secret key provided by AWS team 

2. Created Service accounts  and did discover datacenter and all the datacenter and sub accounts are getting populated in Servicenow

3. Created Discovery schedule with cloud Resource type and ran the discovery, Discovery are completed with AWS datacenters and cloud service account but VMs are not discovered.

We have checked discovery log and ecc queue but it is not throwing any such errors.

Mid server is installed in one of the availability zone of the parent data center in AWS

[Ian Ma]

• First thing to check is if the required patterns are enabled. I've find that sometimes when upgrading the discovery and service mapping pattern plugin, it would de-activate half or more of the patterns, it seems to be common problem originated from the need of some customers that go from CAPI v1 to pattern based.

• It's simple to check, go to pattern designer -> patterns, search for patterns that starts with Amazon AWS -, from memory, there should be none that are inactive. FYI, the pattern that needs to kick off is named "Amazon AWS - Virtual Server (LP)", but there is a chain of patterns that needs to trigger before it for VM instance discovery to start.
• The best way to activate the patterns if they are off is via the "Migrate CPG to Pattern" page.

[Shiksha1]

Could you please suggest resolution as i am also facing same issue.

[Aarti6]

@upasmita @Shiksha1 @Ian Ma 
Please let me know the fix for this issue. I have recently migrated from CAPI to Pattern and since then I am not able to discover the VM instances.

Thanks in advance!!

[Shiksha1]

yes that has resolved my issue