Configuring Connections: Amazon Redshift

Versions: 8.0+

Versions:4.5+

Configuring QuerySurge Connections: Amazon Redshift

When you create a QuerySurge Connection, the Connection Wizard will guide you through the process. Different types of QuerySurge connections require different types of information.

For an Amazon Redshift Connection, you will need the following information (check with a DBA or other knowledgeable resource in your organization):

• Database login credentials (username and password)
• Cluster endpoint hostname (ex. x.y.us-west-2.redshift.amazonaws.com)
• Port (5439 is the default port)
• Database name

Launch the Connection Wizard

1. Log into QuerySurge as an Admin user.
2. To configure a Connection, select Configuration > Connection in the Administrative View tree (at the left).
3. Click on the Add button at the bottom left of the page to launch the Connection Wizard. Click Next.
   
   Note: Check the Advanced Mode checkbox for access to advanced features.
   
   
   
   
4. Provide a name for your connection. Select "Amazon Redshift [Driver Bundled]" as the Data Source.
   
   Note: A Redshift JDBC driver is bundled with QuerySurge, so you can install this driver from the QuerySurge Installer.
   
   
   
   
5. Once you have selected your Data Source, the Wizard will tell you what information you are likely to need in order to create your Connection. Once you have collected this information, you are ready to click Next.
   
   
   
   
6. Provide the connection information to your database. This includes the cluster endpoint hostname, the port (the default port will automatically populate), the database name and the login credentials. Click Next.
   
   Required fields for your Connection Type are marked by an *.
   
   
   
   
7. Click on Test Connection.
   
   Note: You must have an Agent running with the driver for this Connection deployed in order to test the Connection.
   
   
   
   
8. Save the Connection.
   
   
   
   
9. Congratulations! You’ve created a QuerySurge Connection. Again, make sure that you have deployed the driver for this Connection to all your QuerySurge Agents. (See Adding a JDBC Driver to your QuerySurge Agent for instructions.)