Connection environments
Paradime connects to Redshift separately for each environment. You configure one connection per environment in Workspace Settings > Environments.
The connection fields are the same across environments. What differs is the Redshift permissions you grant: the Code IDE connection typically reuses a developer’s access, while the Bolt and Agent environments should each use a dedicated service user with the minimum permissions required.
Suggested permissions
- Bolt
- Agent
We recommend creating a new Redshift user and granting the suggested access required to create tables and views in your production database. Run the script below in Redshift as an In Redshift, after each dbt™ run in production you need to make sure the correct privileges are granted, as Redshift does not support grant on future schemas. The
Account Admin. This set of permissions lets Paradime read from and create tables and views when running production jobs in your Redshift database.paradime_prod_user should be able to read new schemas created in your production runs. Check this guide on using grants and hooks.Add a connection
- Click Settings in the top menu bar of the Paradime interface to access Workspace Settings.
- In the left sidebar, click Environments.
- Click Add New next to the section for the environment you are configuring:
- Code IDE for the Code IDE connection
- Bolt for the Bolt connection
- Agent for the Agent connection
- Select Redshift and choose an authentication method.
Authentication methods
Username and password
Connect with a Redshift username and password. Available in all environments.
IAM
Connect using an IAM profile configuration. Code IDE only.
Related
Optional connection attributes
Set additional
profiles.yml attributes for this connection.AWS PrivateLink
Connect privately over an AWS VPC endpoint.