AWS Cloud Discovery not working for Virtual Machines
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-24-2020 06:23 AM
We are trying to set up Cloud Discovery for AWS and running into two distinct problems:
1. The discovery returns a significant number of Cloud Resources but no CI Resources. It does not create any CI (regular discovery automatically creates CIs)
2. No Virtual Machines are returned. Whenever running the schedule for Virtual machines it gets automatically cancelled, with the error "The Discovery range is empty." However, there is a range set up.
Any ideas?
Thank you,
Nick

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-22-2021 06:13 PM
this runs in the first schedule itself - "we automatically call the server discovery on VM/Compute instances picked up during cloud discovery, through the IPs available".
of course the caveats in the blog post apply - please read over.
you can check the cmdb_ci_server* tables and see if these host instances are appearing.