Thank you for your feedback.
Form temporarily unavailable. Please try again or contact to submit your comments.

Discover and view AWS resources

Log in to subscribe to topics and get notified when content changes.

Discover and view AWS resources

After you create AWS accounts, run Discovery to discover AWS accounts and associated resources. Discovery of Amazon Web Services cloud is based on account information rather than an IP range. MID Servers are not used in this type of discovery.

Before you begin

Role required: aws_admin or cloud_admin

Amazon Web Services account credentials

About this task

In AWS, a web service account is a master account that has many subscriptions, where each subscription is a set of login credentials. Each subscription has views into the resources available in the master account to that subscription. To discover the entire web service account, you must have the credentials for each subscription.
A Discovery schedule can discover one or more AWS accounts. To perform host-based discovery of the virtual hosts contained within an AWS Virtual Private Cloud (VPC):
  • A MID Server must be installed and configured on a node within the VPC.
  • Each VPC that is discovered must have a separate Discovery schedule for the IP addresses in the VPC.
Note: Running multiple scheduled jobs at one time can cause significant performance degradation. When possible, schedule cloud discovery, billing data download, and resource optimization jobs to run a few hours apart instead of overlapping. To view scheduled jobs, navigate to System Definition > Scheduled Jobs.


  1. Navigate to the account to discover: Either: Amazon AWS Cloud > Configuration > Accounts or AWS Discovery > Accounts.
  2. Select the account to discover and click the Create Discovery Schedule related link.
  3. On the Discovery Schedule page, click the Discover now related link.
    The system performs the Discovery process and lists the results in the Discovery Status list. Discovered resources are listed on the Account page, grouped by type on separate tabs.

    The current state of the resource, if applicable, is updated accordingly (for example, EC2 virtual machine instances, AWS VPCs, AWS subnets, etc.).