3回答
- 新しい順
- 投票が多い順
- コメントが多い順
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!
回答済み 2年前
0
Same problem here. Production database has started modification without any prerequisites. Because of that modification, production Redshift cluster is unreachable anymore.
回答済み 1年前
関連するコンテンツ
- 質問済み 6年前
- AWS公式更新しました 3年前
- AWS公式更新しました 6ヶ月前
- AWS公式更新しました 1年前
- AWS公式更新しました 2年前
How did you solve this? I'm facing the same problem with Redshift serverless. I could not query data and delete the namespace/workgroup.