Cloud Discovery

Overview

When you create a Cloud Discovery schedule, you select the accounts to discover, the credentials for accessing these accounts, and the MID Servers to scan the cloud resources. You can then view the results of the Discovery in a dashboard and track any errors that might have occurred.

Supported cloud providers (Orlando Release)

• Amazon Web Service (AWS)
• Microsoft Azure
• Google Cloud Platform (GCP)
• IBM cloud
• VMware cloud

Cloud Discovery Setup Steps

1. Install Mid Server: Make sure you have all necessary access to your network.
2. Set up Credentials: Select the correct type of credentials.

If you are setting AWS credential then you will be ask to fill “Access Key ID and Secret Access Key”. You will get this from your client.

3. Set up Service Account: Set service account and associate the credentials on it. You can provide the information for an existing account or add an account. Select your cloud credentials and test the connection to your account. A successful credential test returns a list of available sub-accounts that you can include in your schedule.

4.Datacenters: Select specific datacenters in your account to discover or configure Discovery to automatically include all current and future datacenters.

5. Schedule: Create a Cloud Discovery schedule. You can run your schedule immediately from the Discovery Manager or exit the configuration and let Discovery run as scheduled.

6. If Using a MID Server through a proxy: If your MID Server must go through an unauthenticated proxy server to access cloud resources, you must modify the agent\conf\wrapper-override.conf file, as follows:

As with any changes to the MID Server files, restart the MID Server and then test Discovery.

Amazon Web Services Discovery

1. Discover Configuration Items Hosted on Amazon Web Services  Discovering infrastructure and application configuration Items (CIs) and their attributes that are hosted on Amazon Web Services (AWS) is the same process as configuring horizontal discovery to discover CIs that are hosted in an enterprises’ own network. We must configure appropriate credentials, schedules, IP addresses or ranges, and a MID Server with access to the various target CIs. As result, horizontal discovery can be executed in order to query and collect information on the various CIs hosted on AWS including their relationships.
2. AWS Service Account Configuration

• To discover resources in an AWS or Azure cloud, a ServiceNow administrator or implementer must configure a series of settings, including credentials and service accounts.
• Unlike the previous example where credentials were configured to discover the actual target CIs (virtual instances) that are hosted in AWS, the credential needed in this example is the one required to access the AWS account itself. 
• A Service Account must be configured which includes information such as the cloud account ID, the configured AWS credential, and datacenter type. In the case of AWS, the datacenter type is AWS Datacenter. 

3. Discover AWS Cloud Resources

After the AWS datacenters are successfully discovered, a discovery schedule can be created to discover the cloud resources of the account, including the AWS virtual instances, state of the of the virtual instances, regions, availability zones, security groups, images, instance types, etc.

After the cloud resources data are discovered, the data is correlated with a relationship of Virtualized by: :Virtualizes to the host CI discovered from horizontal discovery. As a result, the CI in the CMDB and its dependency view map is enhanced to include the data collected from both horizontal and cloud resources discovery to provide a more complete view of the virtual instance running in AWS.