Redshift Troubleshooting
This page lists common errors when you connect Sifflet to Redshift, and how to fix them. Sifflet shows these errors in the test report when you click Test, and in the logs of a failed refresh in the source details.
Connection
Sifflet Can't Connect to Redshift
Symptom
Failed to connect to Redshift. Please check that the host is correct and that your network configuration allows connections from Sifflet IP addresses to the Redshift port.Failed to connect to Redshift: the connection was refused. Please check that the host and port are correct and that your network configuration allows connections from Sifflet IP addresses.Cause
Sifflet can't open a network connection with the cluster or workgroup, most often because the connection times out or is refused: the host or port is wrong, the host can't be resolved, the cluster or workgroup isn't reachable from Sifflet, or the cluster is paused. Your credentials aren't involved in this error.
Fix
- Check the Host and Port fields against the endpoint shown in the Redshift console. See Step 2: Add the Redshift Source in Sifflet.
- Check that the cluster or workgroup is publicly accessible, and that its security groups and network ACLs allow the IP addresses of the Sifflet instance where you create the source. See Network Access. Not applicable if you configured Sifflet with AWS Private Link.
- If Sifflet connects to your Redshift resources through AWS Private Link, check with your Sifflet representative that an endpoint is configured for this cluster or workgroup.
- Check that the cluster is running.
The Host Isn't Recognized
Symptom
No connection pool could be created. This could mean the host is wrong. Please check the integration settings and try again.Cause
The Host field doesn't contain a valid Redshift endpoint, for example because it still contains the port or the database name copied from the console.
Fix
- Copy the endpoint from the Redshift console, and remove the
:<PORT>/<DATABASE>suffix. - Paste the host name alone in the Host field. See Step 2: Add the Redshift Source in Sifflet.
The Default Database Doesn't Exist
Symptom
Database "<DATABASE>" does not exist. Please try again with an existing database.Cause
The Default database field doesn't match a database of the cluster or workgroup.
Fix
- Run
SHOW DATABASES;on the cluster or workgroup to list its databases. - Set the Default database field to one of them, for example
dev.
This field expects a single database name, not a qualified <database>.<schema> schema name.
The Default Database Isn't Valid
Symptom
The Default database field of the source shows this error:
Must be the name of a Redshift database: at most 64 characters, without dots, slashes, backslashes, or any of the characters ? % * : | " < >. A Data Catalog reference (such as awsdatacatalog.my_database) is not a Redshift database name: enter the name of a database of your Redshift cluster or workgroup.Cause
The Default database field contains a value that can't be a Redshift database name, for example a Data Catalog reference such as awsdatacatalog.<GLUE_DATABASE>, or a <database>.<schema> name.
Fix
Set the Default database field to the name of a local database of the cluster or workgroup, for example dev.
The Default Database Is a Shared Database
Symptom
Cannot connect to the shared Redshift database "<DATABASE>" (created from AWS Glue Data Catalog or a datashare). Please use a local database of your Redshift cluster or workgroup.Cause
The Default database field contains a database created from the AWS Glue Data Catalog or from a datashare. Sifflet can't connect to these databases.
Fix
Set the Default database field to a local database of the cluster or workgroup, for example dev.
The default database is only the database Sifflet connects to first. It doesn't restrict what Sifflet can monitor: schemas of other databases, including the awsdatacatalog database for AWS Glue and Lake Formation data, can be selected after you click Load assets. See Step 2: Add the Redshift Source in Sifflet.
Authentication
Authentication Fails
Symptom
Authentication to Redshift failed for user "<USERNAME>". Please check the credentials and try again.Cause
Redshift rejected the username or password of the credential used by the source.
Fix
- Check that the credential contains the username and password of the Sifflet user created in Step 1: Create a Database User in Redshift.
- Click Test again.
IAM Authentication Requires SSL
Symptom
SSL is required for IAM authentication. Please enable SSL in the integration settings.Cause
The source uses IAM authentication, but Enforce encrypted connection (SSL) is unchecked.
Fix
- Check Enforce encrypted connection (SSL) in the source settings.
- Click Test again.
The Serverless Workgroup Isn't Found
Symptom
Serverless workgroup "<WORKGROUP>" not found. Please try again with an existing workgroup.The provided custom domain name is not linked to a workgroup. This could mean the host is wrong. Please check the integration settings and try again.Cause
With IAM authentication, Sifflet couldn't find the workgroup: the Workgroup name or AWS region field is wrong, or the host is a custom domain name that isn't associated with the workgroup.
Fix
- For a standard Serverless endpoint (ending in
.redshift-serverless.amazonaws.com), leave Workgroup name and AWS region empty. - For a custom DNS name or a load balancer host name, set Workgroup name and AWS region to the values shown in the Redshift Serverless console.
- Check that the IAM role is allowed to call
redshift-serverless:GetCredentialson this workgroup. See Alternative: IAM Authentication.
Permissions
The Schema Can't Be Found
Symptom
The schema cannot be found, schema = <SCHEMA>Cause
A schema selected in the source scope doesn't exist anymore in the database, for example because it was dropped or renamed.
Fix
- Click Reset and reload in the scope selector of the source, and select the schemas again.
- Grant the Sifflet user access to the new schemas, as described in Step 1: Create a Database User in Redshift.
Missing Assets
The Connection Succeeds but No Tables Appear
Symptom
The test succeeds and the refresh completes, but some schemas have no tables in the Data Catalog.
Cause
The Sifflet user, or the IAMR:<ROLE_NAME> user for IAM authentication, has no USAGE or SELECT privilege on the schema. In this case, the connection works, but Redshift returns no metadata for the schema instead of an error.
Fix
- Run the grants of Step 1: Create a Database User in Redshift in each database and schema to monitor. For IAM authentication, grant them to
"IAMR:<ROLE_NAME>", or grant access in Lake Formation. - Refresh the source.
Lineage
Warning About svl_statementtext
svl_statementtextSymptom
The test succeeds with this warning:
Redshift lineage table "svl_statementtext" can't be accessed. Field level lineage will not be available.Cause
The Sifflet user can't read SVL_STATEMENTTEXT. On Redshift Serverless, this view isn't available, so the warning is expected and lineage from query history isn't supported.
Fix
- On Redshift Serverless, ignore the warning.
- On a provisioned cluster, grant the optional lineage permissions of Step 1: Create a Database User in Redshift.
Lineage Is Empty on a Provisioned Cluster
Symptom
The test succeeds without warning, but tables have no upstream or downstream lineage.
Cause
The Sifflet user doesn't have SYSLOG ACCESS UNRESTRICTED, so SVL_STATEMENTTEXT only returns its own queries. Or no query has written to the tables recently.
Fix
- Run
ALTER USER <USERNAME> SYSLOG ACCESS UNRESTRICTED;as a superuser. See Permissions Required for what this privilege gives access to. - Wait for the next refresh of the source, after your pipelines have written to the tables.
Updated 10 days ago

