Create an AWS Discovery schedule in Discovery Admin Workspace

Release version: Zurich

Updated July 31, 2025

4 minutes to read

Use the Discovery Admin Workspace dashboard to create an Amazon Web Services (AWS) Discovery schedule.

Before you begin

Verify the following:

You have at least one validated MID Server with a status of Up. The MID Server must reach the IP ranges that you intend to discover. You can install the MID Server by using Use MID Server guided setup or by manually downloading and running the installer. For details, see the MID Server installation instructions for Linux and Windows.
The MID Server used for Cloud Discovery is configured with the Cloud Management capability.
You have created suitable credentials in the ServiceNow AI Platform to connect with the service accounts on which you want to perform the discovery.
Cloud Discovery has adequate permission to discover the resources of the target cloud. For more information on AWS cloud permissions, see Control AWS access and permissions using policies.
You're using Discovery Admin Workspace v1.11.0 or later.

Role required: discovery_admin

Procedure

Navigate to Workspaces > Discovery Admin Workspace > Schedules.
Select New Discovery from the header of any tab on the Schedules page.
Select Cloud-based discovery and select Continue.
Enter a unique and descriptive name for the Discovery schedule.
Select AWS as the cloud provider.

Choose a MID Server.

Option	Description
Use a cluster of MID servers	Select an existing MID Server. Clusters provide failover protection and load balancing between MID Servers. See Configure a MID Server cluster for more information.
Automatically select a MID server	An available MID Server with an Identity and Access Management (IAM) role is automatically selected when the Discovery schedule runs. See Automatic MID Server selection for more information.
Search for a MID server	Choose a MID Server to run the Discovery schedule. Only MID Servers that are validated, up, and have the Cloud Management capability are displayed. Note: If you select this option, you can restrict the search to MID Servers with credential-less Discovery enabled by checking the corresponding box.

Select Next.

Select a cloud account.

Option	Description
Existing cloud account	Select an existing cloud account on your instance. Once an account is selected, the Account name and Account ID fields auto-populate.
New cloud account	Add a new cloud account to your instance by entering an account name and ID.

Choose whether you want to Assume an IAM role or Use permanent credentials.

Option	Description
Assume an IAM role	The MID Server temporarily assumes an IAM role using a trust relationship. After selecting, provide the Access Role Name and account for access. Note: Before entering the Access Role Name and account, verify the following: The IAM role exists on the target account, with the required permissions and policies for Cloud Discovery. The IAM role must trust the MID Server's account so it can assume the role. If these prerequisites aren't met, verification fails. It's best to confirm with your cloud admin that the role and trust relationship are properly configured before proceeding.
Use permanent credentials	The MID Server uses static access keys tied to an IAM user.

Option

Description

Assume an IAM role

The MID Server temporarily assumes an IAM role using a trust relationship. After selecting, provide the Access Role Name and account for access.

Note:

Before entering the Access Role Name and account, verify the following:

The IAM role exists on the target account, with the required permissions and policies for Cloud Discovery.
The IAM role must trust the MID Server's account so it can assume the role.

If these prerequisites aren't met, verification fails. It's best to confirm with your cloud admin that the role and trust relationship are properly configured before proceeding.

Use permanent credentials

The MID Server uses static access keys tied to an IAM user.

Even if the service account was previously verified, you can reverify if policies or permissions may have changed by selecting Verify information.

Select Discover all member accounts or Discover specific member accounts.

Note:
This option displays only when the target cloud account is an AWS management account.
1. If discovering specific subscriptions, select Add member accounts.
  The Discoverable Accounts dialog displays.
2. Select the check box next to one or more corresponding names and then select Add.
Select Next.
Select cloud regions for the discovery schedule.

You can choose to include all regions linked to the cloud account or select specific regions. There’s no restriction on the number of cloud regions that you can add.
1. Optional: To discover specific cloud regions, select the check box for the cloud region you want to scan from the Available cloud regions list.
2. Optional: If the cloud regions don't appear, select Refresh cloud regions.
Select Next.
Optional: To complement your cloud schedule with an IP-based Discovery schedule, enable the Create a server discovery schedule toggle.
1. Optional: Select a method from the Discovery method drop-down list.
  Discover servers with credentials uses operating system (OS)-level credentials to perform deep discovery on EC2 instances. Discover servers with AWS Systems Manager (SSM) uses AWS SSM Agent to perform deep discovery on EC2 instances. The system property glide.discovery.enable_ssm must be enabled to use SSM discovery. For more information, see Enable AWS SSM-based discovery.
2. Optional: Select a MID Server or cluster that can discover the Virtual Machines (VM) and their attributes.
Select Next.

Configure the Discovery schedule.

Option	Description
Run at a scheduled time	The schedule runs at a scheduled date and time. Use the fields to define when the schedule runs.
Run on demand	The schedule only runs when triggered manually. Trigger the schedule by selecting Finish and run at the end of this setup, or by navigating to the schedule in the Discovery Schedules [discovery_schedule] table and selecting Discover Now.
Run after series	The schedule runs after another existing Discovery schedule completes, staggering or chaining them together. Selecting an existing schedule displays a relationship map of all the other associated schedules.
Set discovery time out	If the schedule exceeds the maximum runtime, it's canceled. After toggling, configure the runtime threshold.
Finish and run	After being selected, all the information provided is validated. Then, a Discovery schedule is created in the background, a Discovery status is created, and the schedule is run. You're redirected to the Status Details page for the schedule.
Finish	After being selected, all the information provided is validated. A Discovery schedule is created, and you're redirected to its entry in the Discovery Schedules [discovery_schedule] table. You can edit the schedule information or run it by selecting Discover Now.