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

[Jason82]

I found your post today because we are having the same issue with Google Cloud. When running the schedule created during the setup process it cancels and returns the error The Discovery range is empty.

I saw the same issue when setting up Discovery for Azure. Went through the setup process and received the same error when running the Discovery Schedule created by the setup process. Our implementation consultant noted he has always experienced that. His recommendation was to delete the Discovery Schedules created by the setup process, then open each Azure Subscription and click on the Create Discovery Schedule link under the Related Lists section. It works with no issues.

Google Cloud does not have a similar setup with subscriptions so there is not a Create Discovery Schedule link available. Instead, I manually created a new Discovery Schedule with the same settings as the automatically created schedule, then added our range set. It works with no issues.

Maybe try manually creating a new schedule with the same settings? Seems to work for other cloud resources but we we don't use AWS. I don't understand why it works, but it does.

[reg_1979]

This was the solution for me. I had been working on this problem for 18 months. 

[Timothy Onyskin]

I had to do the same thing with Azure and GCP (remember to check if new subscriptions have been stood up every now and then since it doesn't auto-create new jobs), but AWS isn't supposed to have to work that way.  The way it was explained to me by ServiceNow is that AWS is actually aware of the sub-accounts and therefore will scan each of them automatically.  I am having the issue where no VMs are found and the VM schedule it creates afterwards cannot find any IP address.  I don't know if it is an access issue or a ServiceNow issue.  With GCP and Azure, I could run a manual CLI command to see if I can get all the VMS, but when I do the same sort of thing for AWS, it gives me nothing.  I have a feeling it is my account, but I am not sure how to tell exactly so the cloud guys don't waste their time.  Any help with ServiceNow or the AWS CLI would be most appreciated.

[Ram Devanathan1]

Starting Paris Patch 5, and with the Quebec release we automatically call the server discovery on VM/Compute instances picked up during cloud discovery, through the IPs available. 

Blog here - https://community.servicenow.com/community?id=community_article&sys_id=51ca7751dbac6c10b1b102d5ca961...

[Timothy Onyskin]

That is where my problem is.  That second job cancels immediately stating "The Discovery range is empty."  I am on Paris Patch 6 Hot Fix 1.