3 Answers
- Newest
- Most votes
- Most comments
2
FYI, I opened up a trouble ticket and they told me that I will need to delete the cluster and create a new one from backup. If you use the same cluster name, the endpoint will also be the same. It will have a different IP, but the conx string should be the same.
edit: My redshift instance finally came back online!
answered 2 years ago
1
Same problem here. Ours is stuck in Modifying too since the outage yesterday.
answered 2 years ago
0
Same problem here. Production database has started modification without any prerequisites. Because of that modification, production Redshift cluster is unreachable anymore.
answered a year ago
Relevant content
- asked 2 years ago
- asked 2 years ago
- asked 9 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 22 days ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
How did you solve this? I'm facing the same problem with Redshift serverless. I could not query data and delete the namespace/workgroup.