AWS SG Connector not returning Organization ID or accounts

Nikita Thomas1
Tera Contributor

Hi,

 

I have configured the AWS SG Connector for a customer and when testing the connection, it is successful with a code of 200. 

Now when I run the diagnostic tool, the status again shows Passed and the Diagnosis State = Completed. However, the message I get is "No accounts found to perform API access test". I have tried to troubleshoot this with my AWS customer contact but we have exhausted all the possible scenarios.

 

On trying to view the diagnostic details in the "sn_aws_integ_sg_aws_diagnostic_details" table, there are no results at all. 

 

The diagnostic summary does not point to any error message or failure other than suggesting that no accounts have been found. However, the customer has confirmed they have a fair number of accounts that should be returned via this integration.

 

I've also tried the "Test Load 20 accounts" related link but it only returns the details of the central aggregator account.

 

Has anybody come across a similar issue and been able to resolve it?

 

Any leads would be appreciated.

 

Thanks,

Nikita

 

@Murali Reddy1 Tagging you here as I have seen many helpful articles created by you. Please share any insights that you may have.

4 REPLIES 4

Murali Reddy1
ServiceNow Employee
ServiceNow Employee

@Nikita Thomas1 The diagnostic test completes irrespective of the success or failure to show the job has done. The summary dashboard says how many accounts it got scanned and got response. With your information, it is tough to advise what went wrong. Can you raise a case to investigate the issue?

Hi Murali,

 

Thank you for your response. I will raise a case with ServiceNow.

 

I'm also attaching some snippets of the diagnostic output, if that will help to shed some more information on the issue. Please share your thoughts.

 

Regards,

Nikita

Murali Reddy1
ServiceNow Employee
ServiceNow Employee

@Nikita Thomas1 The screenshot shows something fundamentally wrong with the user account created in your AWS side. Please follow the setup instructions and see if appropriate setup is done in AWS side. 

Pranav Patil
Tera Contributor

Hi @Nikita Thomas1 

Did you get a resolution for this? I have the same results returned from the AWS diagnostic tool with a message as "

No accounts found to perform API access test"

 

Please let me know if you were able to resolve the same , Thanks 

Regards,
Pranav Patil