Performing a cloud discovery run

Before you can perform a cloud discovery run, you must:

1. Create a credential or access key in the tool you use to access the cloud provider. For Amazon Web Services (AWS), this is the AWS Identity and Access Management  (IAM) console.
2. Create a cloud credential in BMC Discovery using the credential or access key you just created.
3. Test the credential.

These steps are described in greater detail in Discovering Amazon Web Services. The following procedure describes performing the cloud discovery run once you have configured and tested your credentials.

To run a cloud scan

To perform cloud discovery from the Discovery Status page:

1. Select Manage > Discovery.

2. Click Add New Run.
   The Add a New Run modal window is displayed.
   
   
   

3. Update the fields as described in the following table:

   Field name	Details
   Label	Enter a label for the discovery run. This label is shown where the discovery run is referred to in the UI.
   Timing	Select Snapshot to run an immediate cloud scan, or select Scheduled and fill in the scheduling information to run a scheduled cloud run.
   Targeting	Select the target for the discovery run. In this case, select Cloud.
   Provider	Specify the type of cloud provider. In this case, select Amazon Web Services. The modal window refreshes with fields appropriate to the provider selected.
   Company	(Optional) If you have CMDB synchronization configured with multitenancy, select the Company to which to assign the discovery run.
   Credential	Select the credential to use for the discovery run. The list is populated with valid credentials for the selected provider. If none are available, add a new one.
   Regions	Click List of regions to scan for a complete list and select regions to scan; for example, EU (Frankfurt). AWS also provides service and regulatory domain groups to scan, enabling you to select all regions in that service or domain.
   System Manager Sessions	Select whether to enable the use of the AWS Systems Manager Agent for the scan.
   Sessions Per Second	Select the number of AWS sessions permitted each second. The default value is three.
   Active Sessions	Select the number of active AWS sessions permitted each second. The default value is five.
   Session Logging	Choose whether to enable session logging for this scan. Session logging captures raw discovery data that can be used to diagnose discovery and data quality issues. The default is not to capture session logs. You only need to capture session logs when raising a customer support case. This option is not available for Scheduled runs. For information on viewing session logs, see If you encounter a problem .

4. Click OK to save the cloud scan settings and close the modal window.
   If you have configured a snapshot run, you can see it running immediately in the Currently Processing Runs tab. If you have configured a scheduled run, it is listed in the Scheduled Runs tab.

To verify results

When you have performed a cloud scan, verify the results as represented in the following screenshot:

The following screenshot represents a BMC Helix Discovery view of the scanned results:

Scanning the hosts

You can perform an AWS host scan in the following ways:

• A regular IP scan that discovers hosts only. For more information, see Performing a discovery run .
• An implicit scan by using AWS SSM (Systems Manager Agent). This scan discovers VMs and related hosts. To initiate this type of scan, enable the System Manager Sessions feature when you configure a discovery run. For more information, see Discovering EC2 hosts by using AWS Systems Manager .