AWS Discovery Failing Due to MID Server Selection Across Multiple MID Servers with Same Capabilities
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
48m ago
Hi Team,
We are facing an issue with AWS Discovery/Cloud Onboarding where multiple MID Servers exist in the same domain and advertise the same capabilities.
Current setup:
Multiple MID Servers are active in the same ServiceNow domain
All MID Servers share identical capabilities
Discovery/Cloud onboarding is selecting MID Servers dynamically/randomly
Only specific MID Servers have the required access/connectivity/service account permissions
When another MID Server gets selected, discovery fails
Observed behavior:
ServiceNow appears to pick different MID Servers during onboarding/discovery execution
Discovery succeeds only when the expected MID Server is selected
Onboarding itself does not provide deterministic MID selection
Since all MID Servers have the same capabilities, the platform treats them equally
We are trying to identify the best long-term approach to enforce deterministic MID selection.
Questions:
What is the recommended approach for controlling MID selection in this scenario?
Is capability segregation considered best practice for AWS Discovery?
Would MID Server clustering help in this case?
Is there a way to prioritize/prefer a specific MID Server during cloud onboarding/discovery?
Has anyone implemented capability-based routing successfully for AWS accounts/VPC-specific discovery?
Are there any known limitations/issues with multiple MID Servers sharing identical capabilities in the same domain?
Any recommendations, architectural guidance, or best practices would be greatly appreciated.
Thanks!
