AWS Cloud Discovery issue
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-22-2022 12:46 AM
Hi All,
Need your guidance in AWS Cloud discovery.
We have started moving from On-Prem--> Cloud [AWS]. As per the documentation, we are created below credentials
1. AWS Service Account , 2. AWS credentials.
We have created AWS job schedule and are able to discover the cloud resources. But currently we do have 500+ Server Cis but we are unable to discovery Server CIs[Windows/Linux] as part of this job schedule.
Questions:
1. To discovery the Server CIs[Windows/Linux], Do we need to inform Cloud Ops team to congifure our windows/Linux Credentails in each ec2 instance? Currently in On-Prem, whenever the server is built, the server Build team will configure our windows/Linux credentials in each machine respectively.
Note: our Mid Server is installed in the Cloud.
Please let me know if i am missing any configuration steps.
Regards,
Anitha.
- Labels:
-
Discovery
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-23-2022 11:14 AM
Hi PavanBV,
Thanks for the response. I have created 2 jobs has mentioned. but still the server CIs are not discovered.
Few questions :
1. In AWS Cloud, we do have nearly 500+ server[Windows/Linux], Does any permission needs to provide by Cloud Eng.team to get these CIs to be discovered in ServiceNow?
Thanks,
Anitha.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-25-2022 03:14 AM
Hi Anitha, you don't need explicit permissions for server discovery. You just need to ensure the firewall clearance, ensure credentials are in place(configured on servers) and the mid server can run wmi/ssh commands against target servers and get the results. This will do the job for you.
Few ques from my side.
1) Are those 500 servers in same Aws account or different accounts
2) What mode of discovery have you implemented - credential based or credential less based?
3) Have you tried running a sample wmi and ssh commands and see if the results are getting populated.