AWS Cloud Discovery not working for Virtual Machines

[odinx16]

We are trying to set up Cloud Discovery for AWS and running into two distinct problems:

1. The discovery returns a significant number of Cloud Resources but no CI Resources. It does not create any CI (regular discovery automatically creates CIs)

2. No Virtual Machines are returned. Whenever running the schedule for Virtual machines it gets automatically cancelled, with the error "The Discovery range is empty." However, there is a range set up. 

Any ideas?

Thank you,

Nick

[Ashutosh Munot1]

Hi,

1) Where you CI that it returns NO CI Resource? how you are validating it.

2) VM discovery error is right: because on your VM you need credentials like Windows , Linux,etc with proper access and then you also need IP address populated on this VMs and they should be added as Ranges in this Schedule.

Thanks,
Ashutosh

[Nick9]

I do not understand what are you asking in #1. As for #2, I do have ranges - and I do have credentials saved in Discovery -> Credentials. I do not see how I can enforce the use of those credentials on this particular schedule.

Regards,

Nick

[Vivektietsood]

Please try the answers in this thread:

https://community.servicenow.com/community?id=community_question&sys_id=1b397a4adb5790146621d9d96896...

[Vivektietsood]

Were you able to resolve this using the link I gave ? Please accept solution so that it helps others with a similar question too. Pasting link here again.

https://community.servicenow.com/community?id=community_question&sys_id=1b397a4adb5790146621d9d96896...