The Connection Dialog and the fields available there ( host, port, user, database, SSH ) are explained in the Connection dialog page.
In the AWS Console, look for the 'Connect Client' tab. There you can get the JDBC connection string.
This string has to be used in the DbSchema Advanced tab / Enforce Custom URL.
How to Create A RedShift Cluster
After logging in AWS Console, you may know about:
- EC2 - is the computing infrastructure. Here you will find all resources related to security (firewalls).
- S3 - is a storage infrastructure, but on a key-value principle
- Security Group for setting firewall rules. This is available under EC2 / Network / Security groups.
Each database, web server or other resource is created in a default security group.
If two resources ( database and webserver ) are in the same security group, they will be able to communicate one
For communication with public internet, you need to create a new security group and add Inbound rule for connecting from
the public IP. Outbound rules are set by default.
- Elastic IP - is a fixed IP you can use for your resource. If for example you integrate an
AWS Redshift database with another external application, you may need an Elastic IP for setting a stable internet connection.
Testing Redshift you don't need this. This service costs.
Create the Security Group
The security group can be created under EC2 / Network/ Security.
Create a new security group and add inbound rule for the Redshift database port.
There is no need to create an outbound rule, as this is enabled by default.
Create the Redshift Cluster
Choose Redshift / Quick Launch Cluster / Switch to Advanced Settings
Choose the cluster name, database name, etc.
A single node instance is fine.
In this step choose:
- Public Accessible - YES
- Security Group - The group created in the previous step
After the cluster is created you can connect from DbSchema using the JDBC connection string from the AWS console.