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
You can create schedules to discover resources for these cloud providers:
How Cloud Discovery works
You select an existing service account to discover in a wizard called the Discovery
Manager. Select the appropriate credentials for the account and then test the connection. If
the connection is successful, Discovery returns the logical
datacenters associated with the account, as well as any sub-accounts for selection. The
cloud schedule creation process launches the necessary patterns to discover the sub-accounts
and datacenters you select.
The Discovery Manager offers you the option to discover your cloud resources (virtual
machines).
Cloud Discovery by IP ranges finds all the VMs in a cloud service
account. Just select a
MID Server configured for
Cloud Discovery and create the schedule.
Discovery determines the IP addresses to scan,
based on the IP ranges in your cloud service account. Make sure you have one or more
MID Servers up and running that can access those addresses.
Note: You do
not need the
Cloud Management plugin to use
Cloud
Discovery. The
Discovery plugin includes the necessary components from
Cloud Management to perform
Cloud Discovery.
Managing your cloud resources
The instance displays all results from a Cloud Discovery
in the Discovery Home page. You can drill down
into specific schedules, discovered devices, cloud resources, and errors. Sort these results
for a closer look and view Discovery trends for the devices you find. Error results give you specific suggestions
for fixing any problems you encounter.
Your instance can detect notifications and alerts from
AWS
cloud,
Microsoft Azure and
Google Cloud Platform (GCP). You can
configure these events to make the necessary updates to your CMDB without additional
scanning.
For more information on configuring Event-based discovery, see
Note: Event-driven Discovery for AWS, Microsoft Azure Cloud and Google Cloud Platform does not
require the Cloud Provisioning and Governance plugin.
Cloud Discovery process
- Install and validate a MID Server using the procedure in
MID Server
installation. If you do not have a MID Server running in your environment, you can use Guided Setup to quickly install and validate a MID Server. Make sure you configure Cloud Discovery
MID Server with the Cloud
Management
capability.
- Open the Discovery Manager and configure the following:
- Service
account
- 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.
- Datacenters
- Select specific datacenters in your account to discover or configure Discovery to automatically include all current and
future datacenters.
- Virtual machine (VM)
resources
- Optionally, configure the schedule to discover VM resources by IP address. Discovery returns additional information about the VMs,
including installed software and running applications.
Note: For the Cloud Insights application, Cloud
Discovery does not display the Discover Virtual Machines
(optional) phase in the Discovery Manager tab bar.
- 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.
- View Discovery results on the Discovery Home page. You
can view details for:
- Schedules
- Discovered devices (VMs)
- Cloud resources
- Errors
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:
wrapper.java.additional.1=-Dhttp.proxySet=true
wrapper.java.additional.2=-Dhttp.proxyHost=<proxyHost>
wrapper.java.additional.3=-Dhttp.proxyPort=<proxyPort>
wrapper.java.additional.4=-DuseProxy=true
As with any changes to the MID Server files, restart the MID Server and then test Discovery.
