Error while Discover datacenter for AWS cloud account

Nithin21
Tera Expert

Steps followed in Servicenow:

1. Create AWS account
Then, create user with Programatic access and Permission = AdministratorAccess.
Make note of the below
AWS Credentials
Account number
Access key
Secret key
 
2. Activate Cloud Management plugin in Servicenow
    Add role "sn_cmp.cmp_root_admin" to user for All access to Cloud Management
3. Set up service accounts with credentials in Servicenow
  • Orchestration -> Credentials -> New -> AWS Credentials
  • Cloud Management -> Service Account -> New                        
5. Set up cloud accounts using Cloud Admin Portal
Cloud Admin Portal
    -> Cloud Account -> New -> Provider = AWS
 

When i click "Discover Datacenters", I get the following error 

 

find_real_file.png

1 ACCEPTED SOLUTION

Vini
Giga Guru

Hey Nitin,

 

We also got the same error at the initial setup of AWS Discovery. Please check the following.

 

  1. Please make sure to Install AWS MiD server with in VPC network of AWS region.
  2. AWS credentials should have IAM permissions.
  3. Make sure to add "Cloud management" and "AWS "capabilities on MiD Server and "Discovery" on Application section. (This causes error in our case).
  4. 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.

View solution in original post

6 REPLIES 6

Alberto Consonn
ServiceNow Employee
ServiceNow Employee

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

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

Vini
Giga Guru

Hey Nitin,

 

We also got the same error at the initial setup of AWS Discovery. Please check the following.

 

  1. Please make sure to Install AWS MiD server with in VPC network of AWS region.
  2. AWS credentials should have IAM permissions.
  3. Make sure to add "Cloud management" and "AWS "capabilities on MiD Server and "Discovery" on Application section. (This causes error in our case).
  4. 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.

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