Redshift new query and database monitoring - broken with 400 HTTP error in Javascript code

Question

Hi! I'm trying to open a connection to Redshift database in the new query and database monitoring, using Secrets Manager credentials. I'm getting a 400 error logged to the JS console. AWS Console is get stuck - I don't get any visible error message.

Is this a bug on your end? If not, I'd appreciate a visual feedback with the clear error description.

The old query and database monitoring is working fine but it will be deprecated on March 21st.

```
{
  "contentString" : "{\"ClusterIdentifier\":\"redshift-data\",\"Database\":\"our database\",\"Sql\":\"select 1;\",\"SecretArn\":\"stripped\",\"StatementName\":\"Client: RedshiftQueryEditor-Login\"}"
  "headers" : {X-Amz-User-Agent : "aws-sdk-js/2.1623.0 promise", Content-Type : "application/x-amz-json-1.1", …}
  "method" : "POST"
  "operation" : "executeStatement"
  "params" : {}
  "path" : "/"
  "region" : "eu-central-1"
}
```

main.js:1290 
 POST https://eu-central-1.console.aws.amazon.com/redshiftv2/api/ketchup 400 (Bad Request)
handleRequest	@	main.js:1290

re:Post Agent · Answer

The 400 (Bad Request) error you're encountering when trying to open a connection to Redshift using the new query and database monitoring interface suggests there might be an issue with your request or configuration. Here are a few things to check:

1. Ensure that your Secrets Manager credentials are correctly set up and have the necessary permissions to access the Redshift cluster.

2. Verify that your VPC and security group settings allow the connection from the AWS Console to your Redshift cluster.

3. Check if your browser's security settings, particularly those related to cookies and third-party content, are not blocking the connection. Some browsers' privacy features can interfere with the AWS Console's ability to establish connections.

4. Try refreshing your connection with AWS IAM Identity Center. You can do this by right-clicking your Redshift database instance and choosing "Refresh."

5. If you're using a Redshift Serverless workgroup, make sure it's not in a paused state.

6. Ensure that your IAM role has the necessary permissions for Redshift, including describing clusters and, if applicable, listing workgroups and namespaces.

If the issue persists after checking these points, you may need to contact AWS Support for more detailed troubleshooting, as the specific cause of the 400 error in your case may require deeper investigation.  
**Sources**  
[The new version 2 redshift connection for Glue fails | AWS re:Post](https://repost.aws/questions/QUfAEVnkwyRo2QVJi86FLU-Q/the-new-version-2-redshift-connection-for-glue-fails)  
[Troubleshooting connections from Amazon Redshift query editor v2 - Amazon Redshift](https://docs.aws.amazon.com/redshift/latest/mgmt/redshift-iam-access-control-idp-connect-troubleshooting.html)

Redshift new query and database monitoring - broken with 400 HTTP error in Javascript code

Add your answer

Relevant content