
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-03-2019 10:46 PM
Steps followed in Servicenow:
- Orchestration -> Credentials -> New -> AWS Credentials
- Cloud Management -> Service Account -> New
When i click "Discover Datacenters", I get the following error
Solved! Go to Solution.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-04-2019 05:21 AM
Hey Nitin,
We also got the same error at the initial setup of AWS Discovery. Please check the following.
- Please make sure to Install AWS MiD server with in VPC network of AWS region.
- AWS credentials should have IAM permissions.
- Make sure to add "Cloud management" and "AWS "capabilities on MiD Server and "Discovery" on Application section. (This causes error in our case).
- all the remining mid servers should not have capability "ALL" or "Cloud management" and "AWS "capabilities.
Let me know if you still have any queries, hope this fix your issue!!!
Thanks & Regards,
Vinil.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-03-2019 11:36 PM
Hi,
you need MID server as mandatory to get any cloud resources.
Follow the procedure described in the official documentation below:
Set up MID Servers to connect Cloud Management to an AWS account
If I have answered your question, please mark my response as correct so that others with the same question in the future can find it quickly and that it gets removed from the Unanswered list.
Thank you
Cheers
Alberto
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-08-2019 10:40 AM
Hi Alberto
When we are configuring the Mid Server, what should be the Account.
I am facing the same issue but I am not sure how the mid server should be configured.
For other discovery, I am using a service account with mid server role.
Can you please guide me about that
Thanks
Vijay

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-04-2019 05:21 AM
Hey Nitin,
We also got the same error at the initial setup of AWS Discovery. Please check the following.
- Please make sure to Install AWS MiD server with in VPC network of AWS region.
- AWS credentials should have IAM permissions.
- Make sure to add "Cloud management" and "AWS "capabilities on MiD Server and "Discovery" on Application section. (This causes error in our case).
- all the remining mid servers should not have capability "ALL" or "Cloud management" and "AWS "capabilities.
Let me know if you still have any queries, hope this fix your issue!!!
Thanks & Regards,
Vinil.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-21-2019 02:19 AM
Hi Vinil,
I followed all the steps, still datacenter's are not populating. In ECC queue, i observe Output & Input records with Name "Executing API DSL for correlation id", in the input record i could see the result returned from api call, which is in base64 encoded format, when i manually decoded, i observed that it is the list of regions. So i'm getting the result from discovery. However, in cloud portal datacenters are not populated & stuck with in progress. Can you help me on how to fix this?
Thanks