AWS .Discovery using IAM Role

[Sonu]

I have setup the environment for IAM role based Cloud discovery for AWS , however post service account creation im not able to discover the datacenter which is the first step .

not sure of the issue here im facing, earlier search found that its due to credentials however in IAM role based i dont see creds being a major contribution here. 

Logs:

Failure while processing chunk : ChunkedStepResult{correlationId='447890-44903b78-7d3c-4d5c-b594-fc7209c7cf75', error='Unable to execute HTTP request: Connect to ec2.amazonaws.com:443 [ec2.amazonaws.com/xx.xx.xx.xx] failed: Read timed out', output='null', chunkNumber=1, totalChunks=1, isRouteComplete=false, exception=null}: com.snc.cloud.mgmt.modules.svccatalog.orchestration.BPOException: Unable to execute HTTP request: Connect to ec2.amazonaws.com:443 [ec2.amazonaws.com/xx.xx.xx.xxx] failed: Read timed out: com.snc.cloud.mgmt.modules.svccatalog.orchestration.result.StepResultHandler.checkCAPIReturnStatus(StepResultHandler.java:264)
com.snc.cloud.mgmt.modules.svccatalog.orchestration.result.StepResultHandler.validateResult(StepResultHandler.java:164)

Env:

The aws environment is a SSO based for authentication, kindly help on this..

in earlier. accounts i havent faced this specific issue while setting up IAM role based.

need more clarity on this .

[Sonu · Accepted solution]

from mid server once the FW was open for ec2.amazonaws.com it started working.

as an update can someone update the Servicenow documentation mentioning this URL as a preReq for AWS discovery , because in environments air gapped environments challenges like these are faced in recent times to to security constrains 

[Ram Devanathan1]

Thank you for this note - please add this comment to the doc page by using the thumbs-up/thumbs-down icon so it can be tracked as a doc task.

Ram

[Sonu]

Done