Issue in AWS discovery
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
5 hours ago
I want to discover my AWS network. For that, I am using ServiceNow ITOM (Australia release). I have installed the MID Server on an AWS server, and it is up and validated. Additionally, when I configured and tested the credentials (SSH private key) for the account, they were validated as well. However, when I try to run the discovery, I face the issue shown in the attached pictures. To correct this, I have removed all discovery affinity records, created a credential with the "ec2-user" (which is unique and has the highest priority), and configured capabilities on the MID Server, but its values are still empty. Please tell me how I can correct this and get my discovery to run successfully. Also when i tried the same in Zurich then it was working perfectly.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
44m ago
Hi
Happy to provide my input. However, the screenshots shared do not contain enough error details to accurately determine the root cause.
Could you please verify that the SSH credentials have the required permissions and that credential validation is successful in ServiceNow? Additionally, if possible, share the complete error message, as this would help in understanding the issue better and identifying the underlying cause.
