Announcing the Saviynt Knowledge Exchange unifying the Saviynt forums, documentation, training,
and more in a single search tool across platforms. Read the announcement here.

AWS Connection failed

sksuresh2k20
New Contributor
New Contributor

Hi Team,

We are getting Connection failed error when testing the AWS PAM integration; please advise  

9 REPLIES 9

DixshantValecha
Saviynt Employee
Saviynt Employee

I appreciate you reaching out to the Saviynt forums.

When you receive a "Connection failed" error when testing an AWS PAM integration, it usually means that there is an issue with the connection between the Saviynt platform and the AWS environment. There are several potential causes for this error, including:

  1. Incorrect credentials: Double-check that the AWS access key ID and secret access key you entered in the Saviynt platform are correct and have the necessary permissions.

  2. Network connectivity: Ensure that the Saviynt platform can reach the AWS environment and that there are no network issues or firewalls blocking the connection.
  3. AWS service status: Check the status of the AWS services you are trying to connect to and ensure they are available and not experiencing any issues.
  4. Integration settings: Review the integration settings and configuration to ensure that they are set up correctly.

Please validate and let us know if further assistance is needed on this.

 

Hi DixshantValecha,

Appreciate your response!
I have validated WS access key ID and secret access key and verified the communication; unfortunately still its failing.

Pelase advise 

 

arpit_b
Saviynt Employee
Saviynt Employee

Hi SK,

One of the common cases of connection failure can happen due to pre requisites missing. The documentation here can help you validate the pre requisites for the capabilities you want to use the connector for https://docs.saviyntcloud.com/bundle/AWS-v231/page/Content/AWS-Preparing-for-Integration.htm

Please validate and let us know if further assistance is needed on this.

Thank you, Arpit , I have followed the doc, and below is the configuration and screen shot,Still have the same issue 

aws.cloud.depoyment=true
aws.cloudformation.template.enabled=true
aws.saas.enabled=true

aws.saas.accountid=064670072339

aws.saas.rolearn=arn:aws:iam::064670072339:role/SaviyntAWS-SaviyntAWSRole-12YTCZTWBHIGB

aws.saas.rolestackname=SaviyntAWS

aws.saas.firstCrossAccountRoleArn=SaviyntAWSRole

 

sksuresh2k20_1-1677103653964.pngsksuresh2k20_2-1677103663053.pngsksuresh2k20_3-1677103667294.png

 

 

Hi SK,

Was there a restart of the services performed after making these changes ?

Thanks

Hi Arpit,

Yes, I have restarted the server after modified the configuration file 

any Idea about this issue while testing connnection 

"Error While Test connection: object references an unsaved transient instance - save the transient instance before flushing: com.saviynt.ecm.identitywarehouse.domain.Securitysystems; nested exception is org.hibernate.TransientObjectException: object references an unsaved transient instance - save the transient instance before flushing: com.saviynt.ecm.identitywarehouse.domain.Securitysystems"

Still connection failed 

NageshK
Saviynt Employee
Saviynt Employee

@sksuresh2k20 Based on the error it appears that the security system associated with the connection may not had been saved properly. Please share more logs to analyze the error properly. Additionally, can you try creating a new connection and check? And if you are using the cross account role to connect to the target AWS Account, then you should not mention a value for "AWS_Stackrole_Name".