You can create an account from Designer or Manager. In Designer, when working on pipelines, every Snap that needs an account prompts you to create a new account or use an existing account. The accounts can be created in or used from:
Your private project folder: This folder contains the pipelines that will use the account.
Your Project Space’s shared folder: This folder is accessible to all the users that belong to the Project Space.
The global shared folder: This folder is accessible to all the users within an organization in the SnapLogic instance.
In Manager, you can navigate to the required folder and create an account in it (see Accounts). To create an account for binary files:
Click Create, then select Redshift > Redshift Account.
Supply an account label.
Supply the necessary information.
URL parameters to be specified to ensure SSL connectivity:
The S3 Bucket, S3 Access-key ID and S3 Secret key properties are required for Redshift-Bulk Load and Redshift-Bulk Upsert Snaps. The S3 Folder property may be used for the staging file. If the S3 Folder property is left blank, the staging file will be stored in the bucket.
(Optional) Supply additional information on this account in the Notes field of the Info tab.
Avoid changing account credentials while pipelines using them are in progress. This may lead to unexpected results, including locking the account.
If the Snap fails to connect to the database, it will retry three more times.
While selecting an Account on a Redshift SSL instance, you can use the JDBC driver v184.108.40.2065 or greater to validate it. However, when not using the Amazon's Redshift JDBC driver v220.127.116.115 or greater, you would be required to manually import an updated certificate into their TrustStore or, simply use the Redshift SSL Account.
Redshift IAM Account Setup
If the EC2 plex (where your Pipeline is running with IAM role), Redshift cluster, and S3 bucket are in the same AWS account, then you must use Redshift Account (normal IAM account).
If the EC2 plex (where your Pipeline is running with IAM role) is in one account and the Redshift cluster and S3 bucket are in a different AWS account, you must use Redshift Cross-account IAM role Account to run your Pipelines successfully.