Configure a JDBC connection in DBeaver so you can query Amazon Redshift clusters from the desktop SQL IDE.
Open DBeaver > Database > New Connection. In the driver list pick “Redshift.” Supply cluster endpoint, port (default 5439), database name, user, and password. Click “Edit Driver Settings” if the JDBC driver is missing; DBeaver will download it automatically.
Use the format jdbc:redshift://<host>:<port>/<database>?ssl=true&tcpKeepAlive=true
.SSL encryption is required; tcpKeepAlive
prevents idle timeouts during long analysis sessions.
Click “Test Connection.” Green means success; red means network, credential, or security-group issues.Verify that the VPC security group allows inbound traffic from your IP on port 5439.
After connecting, run a simple sanity check: SELECT current_database(), current_user, version();
to confirm you are on Redshift.
Create a new SQL script tab and run an aggregate query, e.g., daily revenue from the Orders table.Use DBeaver’s results grid to filter, sort, and export to CSV.
Enable keep-alive, set Maximum number of connections to a reasonable value, and use Auto-commit for quick reads.For long-running ETL, turn off Auto-commit and commit manually.
Right-click the connection > Edit > General > “Save password locally.” Export the connection as a .dbeaver
file and share it securely; recipients can import it via File > Import > DBeaver > Project.
.
Yes. Choose the "IAM" auth method in the connection dialog, install the AWS CLI, and configure your profile. DBeaver signs the request with temporary tokens.
Absolutely. Use the generated Redshift Serverless endpoint and follow the same steps; ensure the JAR driver version is 2.1.0+.
Edit the connection > Driver Properties > set defaultRowFetchSize
. Values of 10 000–50 000 balance speed and memory.