AWS Cloud Discovery stopped working and resources not getting Discovered.

[Kiran A]

Hello,

We have setup AWS cloud discovery and setup daily schedules to scan all our management and member accounts. It was working well, but all of a sudden, it stopped working and when checked the mid server itself is up and running fine. The Jobs are run daily, but not discovering any resources anymore and getting same error message as below for the jobs pertaining to all the AWS accounts. Not sure if it's an issue from ServiceNow side or AWS side. Kindly help.

[Sandeep132]

Hi Kiran,

The first thing I would check is that if the credentials are still valid. Navigate to Service Accounts and open the AWS service account entry. Click on "Create Discovery Schedule" and you will find "Test Account". If the credentials are still working you will be successful message or you will be seeing error message. In that case contact your AWS admin team and see if there is a change in credentials. Hope this helps.

Also, check this article if the error message is on Member accounts discovery https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0748234

Hope this helps. 

[Kiran A]

Thanks Sandeep. There were few FW rules blocking connection from mid server to AWS URL APIs, when removed, its started working. Also we changed the credential for the management account.

[Kiran A]

Thanks Sandeep. There were few FW rules blocking connection from mid server to AWS APIs. Once removed, it started working. We also changed the credential for the AWS management account.

[Patilan]

hello

what are the FW requirement for the connection ? Is port 443 enough ?