Try our plataform
Redshift SSH

Redshift, created by AWS, is an ideal database for storing large volumes of data. It was developed using Postgres itself (one of the best-known general-purpose databases), but it has a columnar architecture that offers incredible processing speed.

SSH pipeline differs from traditional pipeline in that it connects to the database through an intermediate server, also called a tunnel or bastion.

If you want to connect to Redshift in the regular way, without SSH, follow this tutorial

In this article, we'll show you how to register a Redshift SSH database as a destination on Kondado's platform.

Before adding the database, make sure that the user and the bank server are accessible to our IPs that are listed here and allow the connection to the intermediary server on the port that will be used, then follow the steps below:

1) Login to the Kondado platform

2) Navigate to the add destinations page, click on “New Destination” and select the Redshift SSH destination

3) Fill in your database information as shown below:

  1. Name: This is the internal description of your destination on the Kondado platform
  2. Server Address: The address of your database's intermediary server
  3. Server Port: The passthru server port for your database
  4. Server User: The database passthru server user
  5. Server PEM Key: The text of the file with the PEM key
  6. Database address: Your cluster's server address (can be found on your cluster's AWS page under General information > Endpoint)
  7. Database port: Your cluster's port (can be found on your cluster's AWS page under Properties > Database configurations > Port)
  8. Database User: the username that Kondado will use to enter data into your cluster. This user must have DROP, INSERT, CREATE, ALTER, SELECT and DELETE permissions on tables and schemas (can be found on your cluster's AWS page under Properties > Database configurations > Admin user name)
  9. Database Password: The cluster user's password
  10. Database: the database name (can be found on your cluster's AWS page under Properties > Database configurations > Database name)
  11. Schema: inform a schema or leave the default “public” [1]
  12. Click save and your new destination will be created!

[1] Kondado will try to create the schema with the value informed in the “schema” parameter and if this is not possible (for example, due to lack of permission), the public schema will be used. Even if the schema already exists, Kondado must have permission to create schemas (“GRANT CREATE ON DATABASE db TO user”) if you do not want to use the public schema. For existing schemas, it is also important that the user registered at Kondado has permission to use the schema (“GRANT USAGE ON SCHEMA schema_name TO user;”)