Please Note: This article is part of our historical archive. Because it was published a while ago, some of the information, links, or context may now be outdated.
Are you stuck with ‘can’t connect to the Amazon Redshift query editor’? We can help you with this!
Here, at Bobcares, our AWS customers often report similar queries as a part of our AWS Support Services.
Today let’s see how our Support Engineers resolve this ‘unable to connect to the Amazon Redshift query editor’ issue.
Amazon Redshift query editor
The easiest way to run queries on databases hosted by the Amazon Redshift cluster is by using query editor. After creating a cluster, we can run queries by using the query editor on the Amazon Redshift console.
The following cluster node types support the query editor:
- dc1.8xlarge
- dc2.large
- dc2.8xlarge
- ds2.8xlarge
- ra3.xlplus
- ra3.4xlarge
- ra3.16xlarge
To use different node types for the Amazon Redshift cluster, we can connect to the cluster using an SQL client like SQL Workbench.
Can’t connect to the Amazon Redshift query editor
Now let’s discuss the different errors while accessing the query editor and how our support techs resolve those issues.
Access denied or User not authorized Error
The “User not authorized” or “Access denied” error is due to the lack of permission. So we need to make sure that we have the proper permission to access the Amazon Redshift query editor. We must attach the policies “AmazonRedshiftQueryEditor” and “AmazonRedshiftReadOnlyAccess” to the IAM user that accesses the cluster.
For attaching the IAM policies for the query editor by:
- Firstly, Log in to the AWS Management Console and then open the IAM console.
- Select Users.
- Then select the user that needs access to the Amazon Redshift query editor.
- Select Add Permissions.
- Then select Attach existing policies directly.
- Select AmazonRedshiftQueryEditor and AmazonRedshiftReadOnlyAccess from the policy names.
- Select Next: Review
- Finally, select Add permissions.
504 Gateway Timeout or 502 Bad Gateway Error
The 504 Gateway Timeout or 502 Bad Gateway Error are due to temporary network issues. A Bad gateway error is occurring due to the issues between online servers. If the Amazon Redshift cluster fails to receive a prompt response from an upstream server, causes a Gateway Timeout error.
To resolve these Gateway errors, our support techs follow the below steps:
- Clear the cache and browser cookies.
- Use a different network to connect.
- Use a different browser to connect to the Amazon Redshift query editor.
- Try to reboot the cluster to restart the query editor.
- Monitor the Amazon Redshift cluster workload to check that if any query is using more CPU usage.
- Try to increase the number of nodes on the cluster to manage the workload.
After that, we can retry connecting to the query editor in the cluster.
The query gets terminated by the query editor
We can use query editor for short-running queries(completes within 10 minutes) to prevent query termination. For long-running queries(more than 10 minutes), we can use SQL clients like SQL Workbench/J.
[Need help with more AWS queries? We’d be happy to assist]
Conclusion
To conclude, today we saw how our support Engineers resolve the ‘unable to connect to the Amazon Redshift query editor’ issue.
