AWS Discovery : Unable to discover Server CI's

Keerthy S · ‎08-25-2022

Hi All,

We are migrating from On-Prem to Cloud infrastructure. Need your kind guidance for the below queries.

Currently we are in On-Prem, and we do have our service account configured in each Windows/Linux host machine and we do have credentials for Windows/Linux CIs. When we move to AWS Cloud, Does cloud discovery automatically discovers the Cloud Resource + Server CIs (or) do we need to inform Cloud Engineering Team to configure the Service account in each host machine[Windows/Linux] as we did in On-Prem method.
What is Best practice to discover the Cloud Server CIs[Window/Linux] ? Can we you please guide me with configuration steps.
Issue facing:
- We are unable to discovery the Cloud Server CI's [Windows/Linux]. Schedule job is completed successfully with out error.

Thanks,

Keerthy.

Harneet Sital · ‎08-25-2022

Hi Keerthy,

Currently, we are in On-Prem, and we do have our service account configured in each Windows/Linux host machine and we do have credentials for Windows/Linux CIs. When we move to AWS Cloud, Does cloud discovery automatically discovers the Cloud Resource + Server CIs (or) do we need to inform Cloud Engineering Team to configure the Service account in each host machine[Windows/Linux] as we did in the On-Prem method?

With proper access to the Service Account and if you have the Windows/Linux machine admin/root credentials you will be able to discover the machines and processes/applications running on these VMs along with other cloud resources. You do not need to provide any additional access to the Service Account as the ServiceNow account only discovers the cloud layer but the VM layer is discovered by IP-based discovery which requires you to have admin access credentials to the machines.

Step-by-step guides are available here
Community Article: Amazon AWS Cloud Discovery Step by Step Configuration
Youtube Video: How To - Setup AWS Integration for ServiceNow Discovery and Provisioning
What is the Best practice to discover the Cloud Server CIs[Window/Linux]? Can you please guide me with the configuration steps?
I think the document pretty much covers all the aspects - https://docs.servicenow.com/en-US/bundle/tokyo-it-operations-management/page/product/discovery/conce...
Issue facing:
- We are unable to discover the Cloud Server CI's [Windows/Linux]. The scheduled job is completed successfully without error.
  
  1st check to do will be to check if this is toggled to true then only it will discover the machines
  
  We can further validate this if this is already checked.

Thanks
-Harneet Sital
Request you to please mark my answer as helpful or correct based on the impact
Find all my ServiceNow articles here

Harneet Sital · ‎08-26-2022

Hi @Keerthy S

May I please know if the above has resolved your query? If so, please mark the answer as correct and helpful so the thread can be closed and would help others with a similar query.

Thanks,
Harneet

Keerthy S · ‎08-29-2022

Hi @Harneet Sital ,

First apologies for the delayed response. Thanks for the detailed response. Since I am new to discovery, I need your kind guidance.

I have gone through the documents/video. I have checked the toggle is true to discover the machine. But still I am missing 95% of servers. Please correct me if i missed any steps as mentioned below

Steps covered so far:-

1. Created AWS Credentials in ServiceNow - [Name, Access Key ID, Secret Access Key]

2. Created AWS Service Account - [Name: Account ID, Datacenter type: AWS Datacenter]

3. Created AWS Schedule jobs. 1st Job: AWS schedule. 2nd Job: AWS -VM Schedule , Discovery job running successfully.

Need your kind guidance to below queries:

1. How to Validate the AWS Credentials ? (i.e I'm trying to validating the credentials again)

Once I enter all the information for creating AWS credentials, I do see an option to "Test Credentials' ' , it asks me to enter the IP address, Port, MID Server. I have given a valid IP address( The Windows server is up and running in AWS) , Port: 135 , MID Server: AWS MID Server. i am getting error "This Credentials type cant be tested"

2. After running these jobs,

1st job: ran successfully (In the Discovery Status ID, when i check under "Device" tab... i can see 5K+ CIs are discovered ;

2nd job: Discovered only 100+ CIs.

that too..10% - successfully CIs created in ServiceNow.

90% - Error likes (i) No result returned from probe.

(ii) Adding target to blacklist, no valid credential found for type[Window]

3. In AWS Cloud.....Day to day some teams will create new VMs as per the Business requirement How does ServiceNow discovers the new CIs day-to-day in ServiceNow. While creating new VMs in Cloud, whether our credentials are automatically configured in new VMs (linux or Windows) ? whether we need to inform Cloud Ops team to install our credentials for

4. What level of access, does our AWS Service account ID should have. ? i.e Local admins rights.. etc.. ?

5. To get successful AWS discover, can you please list out the items to be configured. I have listed out few as per my knowledge. Please help me to fill if i missed any.

1. AWS Service Account

2. AWS Credentials

3. MID Server - MID Server is installed in AWS.. MID server is reachable to AWS Linux/Windows CIs.

4. Making sure 135, 22 Ports are opened for all AWS Linux/Windows CIs (if more Ports please let me know)

5. Does AWS Credentials will automatically will discovery all the CIs in AWS Cloud. Or like On-Prem discover, do we need our service account to be installed in each CIs. ?

Apologies for too many questions. Looking for towards your kind help.

Thank you

Regards,

Keerthy

Keerthy S · ‎08-29-2022

Hi @Harneet Sital

Can you please guide me for above query.

Thanks,

Keerthy.