AWS Discovery

Waffle
Tera Expert

Hello,

I am trying to configure Discovery to discover AWS EC2. I have setup the Account, credential, and a schedule. After the discovery is completed, the EC2 instance showed up on the EC2 Virtual Machine Instance. When I clicked into the instance record, some of the details are not captured such as the CPUs, Disks, Disks size, and Memories. But the VM size, Availability zone, Object ID and VPC ID are captured. Are there anything else I need to setup to capture the missing information?

** I don't have the Cloud Management module.

Thank you,

1 ACCEPTED SOLUTION

DuaneNMore
Kilo Guru

The Virtual Machine (cmdb_ci_vm_instance) and the server (let's say cmdb_ci_win_server) are 2 different things and capture 2 types of information. The stuff you described was captured by your AWS discovery and is peculiar to the AWS Virtualization. To capture that other information, you need to run a standard horizontal discovery against the Windows server. 

During the Windows discovery (I am talking probes here, sorry), it will run an Windows - Amazon EC2 probe and if it discovers you are an EC2 it runs the AWS Relationship Probe. During the sensor processing it takes the object_id field and finds looks for the vm_instance with the same object_id and then creates the relationship.

Patterns perform the same basic function in the Windows - Cloud Library and ensuing steps

All the CPU, DIsks, memory information are related lists associated with the cmdb_ci_win_server record, not the vm_instanec record. The relationship probe above connects the server and the vm_instance iwth a Virtualized by::Virtualizes entry in the Relationship table. 

View solution in original post

5 REPLIES 5

DuaneNMore
Kilo Guru

The Virtual Machine (cmdb_ci_vm_instance) and the server (let's say cmdb_ci_win_server) are 2 different things and capture 2 types of information. The stuff you described was captured by your AWS discovery and is peculiar to the AWS Virtualization. To capture that other information, you need to run a standard horizontal discovery against the Windows server. 

During the Windows discovery (I am talking probes here, sorry), it will run an Windows - Amazon EC2 probe and if it discovers you are an EC2 it runs the AWS Relationship Probe. During the sensor processing it takes the object_id field and finds looks for the vm_instance with the same object_id and then creates the relationship.

Patterns perform the same basic function in the Windows - Cloud Library and ensuing steps

All the CPU, DIsks, memory information are related lists associated with the cmdb_ci_win_server record, not the vm_instanec record. The relationship probe above connects the server and the vm_instance iwth a Virtualized by::Virtualizes entry in the Relationship table. 

chuckm
Giga Guru

To add to DuaneNMore, a visual representation of what was described.  The Windows Server CI (created by Horizontal Discovery) and the Virtual Machine Instance CI (created by Cloud Discovery).  When both are discovered the Virtualized by:: Virtualizes relationships is automatically created between both CIs.find_real_file.png

Community article that provides more details on Cloud Discovery verses Horizontal Discovery:

AWS Host Based Discovery

Waffle
Tera Expert

That's exactly what I am looking for. Thanks for the response guys.

mholmes
Tera Expert

This makes sense to me in theory, but I was wondering if there are any tips and tricks to configuring "standard" Horizontal Discovery Schedules for AWS servers? I was under the impression that the IP addresses change.