No Server found in my AWS Server (Cloud Management)

[William Lee]

Began experimenting and exploring the capabilities of Cloud Management. I followed the tutorial video found on the ServiceNow Youtube channel for the initial set up using AWS, and everything seemed to work, but a colleague stated that there was a lack of a server found in the Discovery results. Doubled check the hardware for the cloud and he was right, no server found. Did I screw up the setup? How do I fix this? Wanted to speak to anyone who had run into a similar issue and could provide some guidance.

The AWS instance I am running is an EC2 instance, type t2.micro. Thanks in advance and appreciate the help.

[christianmalone · Accepted solution]

were you looking in the virtual machine instance table? That’s where API cloud discovery will populate. Now running IP based discovery will discover the Linux and Windows servers running on ec2 and all the additional info you can’t get from AWS hypervisor. The new cloud discovery quick start homepage allows you to autorun IP discovery automatically after doing cloud discovery. You might be missing OS creds.

[DaveHertel]

Hi - just to pile on to what Christian already said...  IP-based discovery PLUS Cloud Discovery is needed to get the full IT picture of the cloud ecosystem.  This point is not very well communicated (in my humble opinion) on the docs and material.   The cloud discovery implies that it gets 'everything'.  Inaccurate.... and can be puzzling.  Read on:

1. Cloud API discovery gets the Azure/AWS/etc ecosystem.  Like data center, virtual network definitions, image definitions etc.   It does NOT get running VM's, the OS details on the VM, running processes, active IP connections,etc..  
2. IP-based discovery (traditional, horizontal disco) is still need to interrogate (scan) the infrastructure machines running in the cloud to get VM machine details, processes, etc.. the os-level attributes.

Then when both perspectives (API + IP) are discovered and reflected in the CMDB, the SN platform auto-magically <grin> build relationships between cloud stuff and VM stuff, to provide a more comprehensive view (relations, etc.)

Hope this helps?

[chuckm]

To add to christianmalone and Dave Hertel, a visual representation of API cloud discovery and IP based discovery (Horizontal discovery).  The Windows Server CI (created by Horizontal Discovery) and the Virtual Machine Instance CI (created by Cloud Discovery).  When both are discovered the Virtualized by:: Virtualizes relationships is automatically created between both CIs.

Community articles that provide more details on Cloud Discovery verses Horizontal Discovery

AWS Host Based Discovery

AWS Discovery

[calebc]

According to AWS Discovery (thanks for the link), the relationship is based on the matching the values of object_id in both CIs. Are you able to identify what property in Windows it's using for object_id?

I've got IP and cloud discovery working in AWS and no relationships between the guest OS CIs (windows server) and the corresponding virtual machine instance.