Cloud discovery identifies virtual machines and resources hosted in supported public cloud environments. It connects through the provider’s APIs to enumerate resources within the configured discovery scope.
The supported cloud platforms shown are:
Amazon Web Services (AWS)
Microsoft Azure
Google Cloud Platform (GCP)
Oracle Cloud Infrastructure (OCI)
Use this job type to maintain visibility into cloud resources alongside other IT assets. Resource visibility depends on the configured scope and the permissions granted to the cloud credentials.
Example: A cloud administrator creates an Azure discovery job to identify virtual machines within the approved cloud scope and refresh their inventory information periodically.
To create a new job for Storage Area Network (SAN) devices, perform the following steps:
Click Workspace > ITAM > Asset > Discovery > Discovery Jobs.
The Discovery Jobs list page is displayed.Click New Job.
On New Job, select the job type that matches your discovery source.
Figure: New JobJob type
Purpose shown on the selection screen
Network
Discover Windows through WMI, Linux through SSH, and network devices through SNMP.
Cloud
Enumerate virtual machines and resources across AWS, Azure, GCP, and Oracle Cloud.
Container
Discover Docker containers and Kubernetes resources.
Hypervisor
Discover guest VMs through virtualization platforms.
Database
Connect to database engines to discover instances and inventory.
Directory
Discover Active Directory information without an agent.
Storage / SAN
Discover storage systems through supported platform interfaces.
Select Cloud on the new job.
On Identity, select the tenant and enter a descriptive job name.

Figure: IdentityField name
Description
Tenant *
Tenant context associated with the job. The demonstration displays Information Technology.
Job Name *
Name used to identify the job in the jobs list and run details. Example: AWSCloud-Production.
Status
Activation state selected for the job. The demonstration shows Active.
Description (optional)
Purpose, scope notes, ownership, or other context for the team.
Next
Continues to the next wizard stage.
Cancel
Leaves the wizard. Confirm any save or discard behavior presented by the application.
Click Next to open Type and Credentials.
The Type & Credentials step lets you select the Cloud services and associate credentials with the respective Cloud services you want to discover..
For each selected method, add a stored credential. Use quick creation if a suitable credential is not yet available.
Use the up and down controls to arrange the displayed execution order.
Review the methods and selected credentials, then click Next.

Figure: Cloud CredentialsField Name
Description
AWS
Select to discover virtual machines and resources in Amazon Web Services.
Azure
Select to discover virtual machines and resources in Microsoft Azure.
Google Cloud
Select to discover virtual machines and resources in Google Cloud Platform.
OCI
Select to discover virtual machines and resources in Oracle Cloud Infrastructure.
Execution Order & Credentials
Lists the selected providers in their configured execution order, along with their assigned credentials.
Up / Down Arrows
Change the execution order when multiple discovery methods are configured using the arrow keys.
Remove (×)
Remove the discovery method from the job configuration.
Manage credentials
Open credential management to add or maintain credentials for the selected tenant.
Previous
Return to the Identity step.
Next
Continue to the Settings step.
Cancel
Cancel the discovery job configuration.
Create AWS Credential
Enter the credential name, AWS Region, Access Key ID, Secret Access Key, and Session Token.
Click Create & Add.

Figure: Create AWS credentialField Name
Description
Credential Name *
Enter a descriptive name to identify the credential. For example, Storage SAN SNMP Credential.
AWS Region
Enter the AWS Region to discover, such as us-east-1.
Access Key ID
Enter the access key ID for the AWS account identity used for discovery. Leave blank only when the discovery engine host has an instance profile, as indicated on the screen.
Secret Access Token
Enter the secret access key associated with the access key ID.
Session token (STS)
Enter the session token when using temporary AWS Security Token Service (STS) credentials. Use it together with the corresponding temporary access key ID and secret access key.
Create and Add
Saves the credential and adds it to the current discovery job.
Cancel
Close the dialog without creating the credential.
Credential Selection Guidance
Use AWS credentials with read access to the resources being discovered. Specify the AWS Region and provide the matching access key ID and secret access key. For temporary STS credentials, include the session token. Leave keys blank only if the discovery engine host has an instance profile.
Similarly, for Azure, GCP, or OCI you can create the credentials. Parameters may change depending on the Cloud Service Provider for which you are trying to create the credentials.
The Settings screen lets you control cloud discovery performance and diagnostic capture. Configure API concurrency to set the number of parallel API collectors and Job timeout to limit the overall execution duration.
You can also enable Coverage Score to assess collection completeness, Capture Engine Logs to support troubleshooting, and Capture Per-Host Results to retain detailed results for individual hosts. These options help balance discovery performance, visibility, and storage use.
Click Next to configure the discovery schedule.

Figure: Settings | API concurrency, job timeout, and logging
Field Name
Description
API concurrency
Sets the number of API collectors that run in parallel for the cloud discovery job. The displayed value is 10.
Job timeout (hours)
Sets the overall execution time limit for the discovery workflow. The minimum is 24 hours, as indicated on the screen.
Coverage Score
Calculates a per-device score showing which parameters were collected and why others were not. Enable to assess discovery completeness.
Capture Engine Logs
Stores detailed discovery engine logs for each run to support troubleshooting. Enabling this option increases storage use.
Capture Per-Host Results
Stores detailed results for each host, allowing individual results to be investigated by IP address. Disable to reduce storage use.
Click Next.
Execution and Scheduling: The Schedule step lets you define when the discovery job starts, how often it repeats, and when the recurring schedule ends.
Select the effective task queue and if you want to schedule it, enable the Enable Schedule Runs toggle button.

Figure: Scheduling and ExecutionField Name
Description
Effective task queue
Displays the selected worker’s task queue used to execute scheduled runs and Run Now requests.
Enable scheduled runs
Enable to run the discovery job automatically according to the configured schedule.
Repeat Job
Select to repeat the discovery job at the specified interval.
Recurrence Type
Select how frequently the job repeats. The selection shown is Daily.
Recurs Every
Enter the interval between recurring runs. For example, 1 with Daily runs the job every day.
End Condition
Select when the recurring schedule ends. Select No end to continue recurring runs without an end date.
Start Date*
Specify the date and time when the schedule begins. The value is displayed in your time zone and stored in Coordinated Universal Time (UTC).
Previous
Return to the Settings step.
Cancel
Cancel the discovery job configuration.
Create Job
Create the discovery job using the configured scope, credentials, settings, and schedule.
Once you click Scan and Run Now, you will get a message mentioning Job started.

Figure: Job saved successfully