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 Failure - Non-AWS

Alex_Terry
Regular Contributor
Regular Contributor

Hello,

We're currently trying to onboard AWS into Saviynt for our client. With the following connection type "AWS_NonAWSCloudDeploymentCrossAccount_Template" we get an error. Following this documentation: AWS Integration we have configured the connection but when we save and test we get the following popup:

Alex_Terry_0-1715599535559.png

When investigating the logs I get an error (attached). Can you assist?

6 REPLIES 6

rushikeshvartak
All-Star
All-Star

Please share connection configs


Regards,
Rushikesh Vartak
If you find the response useful, kindly consider selecting Accept As Solution and clicking on the kudos button.

Alex_Terry
Regular Contributor
Regular Contributor

The connection type we're using is 'AWS_Non_AWSCloudDeployment_mainAccount_template (AWS)'. As such all the config in the connection is populating fields with specific values and so we can't share them as it's client confidential.

Alex_Terry
Regular Contributor
Regular Contributor

@rushikeshvartak if it's of any assistance in troubleshooting, below I've added the additional lines that I've included in our externalconfig.properties file as well

aws.saas.enabled=false
aws.cloud.deployment=false
aws.cloudformation.template.enabled=false
aws.saas.firstCrossAccountRoleArn=[MASKED]
#aws.saas.accountid
#aws.saas.rolearn
#aws.saas.rolestackname
#aws.sns.topic.arn

Does application restart done post externalconfig updates?


Regards,
Rushikesh Vartak
If you find the response useful, kindly consider selecting Accept As Solution and clicking on the kudos button.

Alex_Terry
Regular Contributor
Regular Contributor

@rushikeshvartak Can you explain what you mean by post externalconfig updates and how to identify if this has occurred?

If you are asking whether we have made those changes to the external properties and then restarted the application, then yes we have performed an application restart and are still seeing the same issue.

Alex_Terry
Regular Contributor
Regular Contributor

Hi, we solved this issue via the support portal. It appears that under the AWS connection type the field 'Connection Attributes as Comma Separated’ didn't contain some of the attributes specified in the documentation. As such we had to run the following A query via an Enhanced Query Execution job to populate the missing attributes required:

 

SELECT 
	EXTERNALCONNECTIONTYPEKEY externalconnectiontype__primarykey,
	REPLACE(ATTRIBUTEKEY,<Old>,<New>) AS externalconnectiontype__ATTRIBUTEKEY
FROM
	externalconnectiontype 
WHERE
	EXTERNALCONNECTIONTYPEKEY=<connection type key>

 

Alternatively you can change the REPLACE function in the above query to CONCAT and just add the additional variables.