AWS discovery is not discovering any VM's
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-18-2020 08:10 AM

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-18-2020 01:49 PM
HI,
Have you debug the issue ? Have you seen the error and debug the pattern for this?
What roles you have to discover this in AWS?
Thanks,
Ashutosh
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-20-2020 02:35 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-20-2020 09:01 AM
Check this link for the pattern log:
Pattern log will give you details on the error
What kind of rights the IAM user has - check in the IAM console for the policy name for this user.
Please like or mark helpful as the case maybe.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-20-2020 09:40 PM
Hey Vivek,
What kind if rights should be given? There is nothing specific on ServiceNow docs, all that docs says is "To discover AWS resources, ensure that the configured credential in the AWS console, has the "ReadOnlyAccess" policy applied." and the same is fulfilled by AW admin.
And regarding the logs, as shown in my screenshot, there are no patterns which ran.So no pattern logs.
Anyhow this is what I see in logs, and which of this will pull the VM?
PS. I am using this option to discover the VMs... Since Discovery automatically selects the IP addresses of the virtual machines in the datacenters which is selected, I am not giving any IP details in my schedule.