- Newest
- Most votes
- Most comments
It sounds like you're experiencing an issue with Amazon Redshift Query Editor V2. While there's no indication of a system-wide outage based on the information available, there are several potential causes for the behavior you're describing.
If your Amazon Redshift Serverless database is in an idle state (auto-paused), this could cause connection issues with Query Editor V2. When a Serverless database is not processing any workloads, it can remain paused when you try to connect, especially when using an AWS IAM Identity Center identity.
Another possibility is an issue with the AWS IAM Identity Center application instance associated with Query Editor V2. If this application was deleted or modified, it could cause the editor to malfunction.
Since you've already tried clearing your browser cache, cookies, using incognito mode, and confirming IAM permissions, you might want to try:
- Connecting with a different authentication method to resume the Serverless workgroup if it's paused
- Check if there are any browser security settings blocking the connection
- Contact AWS Support if the issue persists, as it might require an administrator to delete and recreate the Redshift and Query Editor V2 applications for AWS IAM Identity Center
Query Editor V2 is an AWS-managed application, so all patches and updates are applied by AWS. If there's a genuine service disruption, AWS would typically address it promptly.
Sources
Troubleshooting connections from Amazon Redshift query editor v2 - Amazon Redshift
Redshift Serverless stopped allowing connections | AWS re:Post
Configuration and vulnerability analysis in Amazon Redshift - Amazon Redshift
answered a year ago
Relevant content
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
