Cloud Discovery: AWS and Azure Midservers trying to cross discover.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-12-2023 01:40 PM
We are trying to discover both Azure and AWS environments. We have multiple midservers setup in both environments for segragating Prod, Dev and DR service accounts. We are seeing our aws mids trying to discovery Azure and Azure mids being used to discovery our aws environment. Is this expected? Is there a way to assign mids for the API discovery portion? We have mids that are dedicated to certain tenant and aws service accounts.
Just trying to get a handle on how cloud discovery works vs regular on-prem discovery.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-12-2023 10:44 PM
Hello @Milton3
Yes you are seeing right ServiceNow does that for balancing the ECC queues. When we are configuring Mid server we give the access to Application, Capabilities, IP ranges. (Check this into the related list of Mid Server) For specific MID Server to work on. If your both Mid Servers has ALL Capabilities, Lets say AWS will pick AZURE and AZURE will pick AWS.
So my suggestion will be, you can change the Capabilities of the the specific Mid Server as per there cloud.
For more details visit below link : https://docs.servicenow.com/en-US/bundle/vancouver-it-operations-management/page/product/it-operatio...
Please mark helpful, if my answer is useful to you.
Thanks and Regards,
Anmol Saraswat