Search for	Example	Results
A single word	`cat`	Topics that contain the word "cat". You will also find its grammatical variations, such as "cats".
A phrase. You can specify that the search results contain a specific phrase.	`"cat food"` (quotation marks)	Topics that contain the literal phrase "cat food" and all its grammatical variations. Without the quotation marks, the query is equivalent to specifying an OR operator, which finds topics with one of the individual words instead of the phrase.

Search for	Operator	Example
Two or more words in the same topic	`AND` `and` `+` (plus symbol) `&` (ampersand)	`cat AND dog` `"cat food"+milk` `"cat food"&"dog food"`
Either word in a topic	`OR` `or` `\|` (pipe)	`cat OR dog` `cat \| dog`
Topics that do not contain a specific word or phrase	`NOT` `not` `!` (exclamation point)	`NOT cat` `! dog`
Topics that contain one string and do not contain another	`^` (caret)	`cat ^ mouse`
A combination of search types	`( )` parentheses	`cat + (dog \| mouse)` `cat \| dog + (! mouse)`

Universal DiscoveryContent Pack 27.00 (CP27)

Use > Discovery Modules > Cloud and Virtualization > Cloud > Amazon Web Services Discovery > How to Discover AWS Services

How to Discover AWS Services

This task describes how to discover the low-level AWS services including Auto Scaling Group, CloudFormation, EC2, ECR, ECS, ELB, S3 Bucket, RDS, and VPC, using AWS Protocol.

This discovery process enables you to discover information about running node instances and their configuration (including information about AMI), corresponding block storage, and snapshots with information about regions and zones. All reported topology is in the scope of the Amazon account in which the discovery user is registered.

Note

Support using AWS Identity and Access Management (IAM) users in the AWS credential.
Except AWS GovCloud, the permission for IAM Service is not required.
The AWS Discovery only discovers those AWS components with users' permission.

This task contains the following steps:

Prerequisites - Probe IP address

Discovery requires a probe with at least one IP address in range to trigger.

Prerequisites - Credentials

AWS discovery uses one of three types of access credentials used to authenticate requests to AWS services: access keys.

To represent AWS credentials in UCMDB, you must define: AWS Protocol.

Credential Value	AWS Protocol Name
Access Key ID	Username
Secret Access Key	Password

More information about access keys can be found here.

To discover AWS GovCloud, configure the following parameters in AWS Protocol:

IAM Endpoint: iam.us-gov.amazonaws.com

EC2 Endpoint: ec2.us-gov-west-1.amazonaws.com

RDS Endpoint: us-gov-west-1.amazonaws.com

For more details about these endpoints, see AWS GovCloud (US) Endpoints.

Note For regular AWS discovery, the AWS credential should contain empty endpoints. With such settings, the default endpoints are used for discovery and all regions are discovered. The endpoint parameters are used for the following two scenarios:

Discovery of GovCloud: you must enter specific GovCloud endpoints used by the GovCloud.
Discovery of a specific region only: you must specify the endpoints for a particular region. Refer to the AWS documentation for the list of available regions and endpoints used by them.

For credential information, see Supported Protocols.

Prerequisites - Driver setup
Note This step is required for each probe where you want to run AWS discovery.
1. Download the Amazon SDK for Java from http://aws.amazon.com/sdkforjava/.
  
  The required version is 1.11.75 (referenced as ${VERSION} below) or newer.
2. Unpack the ZIP file to a temporary folder; for example, ${AWS_TEMP_DIR}.
3. Create a folder ${PROBE_ROOT_DIR}/content/lib/aws/, referred to as ${AWS_PROBE_DIR}.
4. Copy the third-party library JAR files and SDK to ${AWS_PROBE_DIR}:
  
  ${AWS_TEMP_DIR}/lib/aws-java-sdk-${VERSION}.jar
  
  ${AWS_TEMP_DIR}/third-party/lib/jackson-annotations-<version>.jar
  
  ${AWS_TEMP_DIR}/third-party/lib/jackson-core-<version>.jar
  
  ${AWS_TEMP_DIR}/third-party/lib/jackson-databind-<version>.jar
  
  ${AWS_TEMP_DIR}/third-party/lib/jackson-dataformat-cbor-<version>.jar
  
  ${AWS_TEMP_DIR}/third-party/lib/httpclient-<version>.jar
  
  ${AWS_TEMP_DIR}/third-party/lib/httpcore-<version>.jar
  
  ${AWS_TEMP_DIR}/third-party/lib/joda-time-<version>.jar
  
  An example of the file structure:
  
  C:\UCMDB\DataFlowProbe\content\lib\aws:
  - aws-java-sdk-1.11.75.jar
  - httpclient-4.5.2.jar
  - httpcore-4.4.4.jar
  - jackson-annotations-2.6.0.jar
  - jackson-core-2.6.6.jar
  - jackson-databind-2.6.6.jar
  - jackson-dataformat-cbor-2.6.6.jar
  - joda-time-2.8.1.jar
Run the discovery

Run the AWS by Web Services job.

Send Help Center feedback