Issue in AWS discovery
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks 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
3 weeks 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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hey,
Thanks for providing your input. I researched this situation and realized a few key points.
Let me explain what I was trying to do. I created an EC2 instance in AWS, installed my ServiceNow MID Server inside it, and was trying to discover that very same instance. I wanted to discover the server where my MID Server is installed because when I previously installed a MID Server locally on my laptop to discover that laptop, it worked perfectly, and a CI for my laptop was successfully created.
However, I have now realized that when discovering a different server on AWS (not the one where the MID Server itself is hosted), that new server is discovered successfully.
Therefore, the conclusion I reached is that a MID Server cannot easily discover the exact same server on which it is installed, but it can discover all other servers and routers on the network.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hey,
Thanks for providing your input. I researched this situation and realized a few key points.
Let me explain what I was trying to do. I created an EC2 instance in AWS, installed my ServiceNow MID Server inside it, and was trying to discover that very same instance. I wanted to discover the server where my MID Server is installed because when I previously installed a MID Server locally on my laptop to discover that laptop, it worked perfectly, and a CI for my laptop was successfully created.
However, I have now realized that when discovering a different server on AWS (not the one where the MID Server itself is hosted), that new server is discovered successfully.
Therefore, the conclusion I reached is that a MID Server cannot easily discover the exact same server on which it is installed, but it can discover all other servers and routers on the network.
