Implementing Cloud Discovery - Initial Setup and Configuration
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-14-2023 02:44 AM
Hi All,
We are implementing cloud discovery for AWS, Azure & Google Cloud. I need help regarding the initial set up and configuration details
1. Through cloud based discovery , we need service account to be setup and each cloud provider has its own set of attributes to be configured. So, for discovering the VMs inside the cloud do we need to configure a separate credential (Like we do for on premises Windows/unix machines) ? If so, what are the level of access required for discovering Windows/Linux VMs and their relationships?
2. Is it possible to configure IP based discovery for VMs alone without having to discover the cloud resources?? if so, what type of credentials is required?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-14-2023 04:39 AM
Where can we find the list of access required for Windows/Unix in documentation? I couldn't find any relevant document. It will be very helpful if you can share any.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-14-2023 03:18 AM - edited 03-14-2023 05:00 AM
the ip discovery run in a network on-premise and the ip-discovery run inside a cloud network are really one and the same technical process - so the access permissions and command access for the OS user are the same as what you would on-prem.
cloud discovery gets more details from the cloud endpoint - so you can connect for instance region, service account to the cloud VM and eventually to the server record (from server discovery). it completes the story. if you are ok with the incomplete story, and only want the server in the cloud then go with ip discovery.