Connection to Redshift Destination Failed

Error Summary

• Hevo cannot establish a connection to the Amazon Redshift Destination due to network or connection setup issues.

Potential Causes

• The Amazon Redshift cluster hosting your database is not publicly accessible, is stopped, paused, or undergoing maintenance.

• The security group of your Amazon Redshift cluster blocks inbound traffic to your port on which your database listens for connections.

  Note: The default port for an Amazon Redshift database is 5439.

• The Amazon Redshift cluster is in a VPC that does not allow network traffic from the public Internet or from Hevo IP addresses.

• The cluster identifier, database name, or port specified in the Destination configuration is incorrect.

• Hevo IP addresses for your region are not added to the Amazon Redshift cluster’s security group.

• The user credentials or role specified in the Destination configuration do not have CONNECT privileges.

• The database cluster identifier points to an endpoint that does not accept network connections.

Suggested Action(s)

• Connect to your AWS account and confirm that the Amazon Redshift cluster is available. If it is paused or undergoing maintenance, wait for it to become available.

• Verify that the Destination connection settings, including the Database Cluster Identifier, Name, and Port, are correct.

  Note: The default port for an Amazon Redshift database is 5439.

• Confirm that your Amazon Redshift cluster is publicly accessible and accepts connections from the Internet.

• Ensure that the Hevo IP addresses for your region are added to the Amazon Redshift cluster security group. If not, refer to the Allowlist Hevo IP addresses for your region section in the documentation for the steps.

• Verify that the Security Group and VPC subnet allow access from all Hevo IP addresses.

• Ensure that the Database User has the required permissions to access your Amazon Redshift database.

• Connect to your Amazon Redshift database using an SQL client, such as DBeaver, with the same connection details and access credentials to test connectivity.

Revision History