AWS discovery without a midserver

[CMDB Nerd]

Hi Folks,

I need to set up API based discovery for AWS. I have already completed the Azure discovery setup(API + IP based). I am not able to find any document which provides API-based discovery(without a mid server) in AWS. My question is: Is it possible to set up AWS API-based discovery without a mid-server in AWS? If yes, can it be done using assumerole capability or it need an account setup in AWS? Please share your thoughts.

Regards

[Sree32]

Try the new AWS Service Graph Connector which can collect the data without MID setup. 

Service Graph Connector for AWS - Introduction
https://community.servicenow.com/community?id=community_article&sys_id=13aa801f1b1ec910c465ece6b04bc...

Service Graph Connector for AWS - Functional Spec and CI
https://community.servicenow.com/community?id=community_article&sys_id=64e2949f1b9ec910c465ece6b04bc...

Service Graph Connector for AWS - Diagnostic Tool
https://community.servicenow.com/community?id=community_article&sys_id=668651e71bde4150c465ece6b04bc...

[Rahul Priyadars]

Basic cloud resources discovery can be done without mid server in aws BUT. The MID server is needed if you want the full 'picture' of the server/infrastructure in the cloud. The Cloud discover uses APIs to get the cloud meta data (vpcs, definitions, images, cloud-related info...) but to get the running details running on a machine, like running processes, installed software on a VM (such as a EC2 server running on AWS) a MID server is needed to do traditional IP discovery. With a MID, the traditional IP discovery to get the details of running machines can't be achieved. The API's of cloud discovery won't provide things like running processes, installed software, machine config details (that are revealed when a machine is scanned via traditional IP discovery) Hope that helps? Taken from old post. Regards RP