- 新しい順
- 投票が多い順
- コメントが多い順
According the support case id which I raised in AWS Support Team the issue was related to operational issue in the Frankfurt
The instance was stuck in stopping state due to the stuck EBS volume. The EBS volume was showing as ‘In Use’ but the instance was showing in stopping state. For EBS volume stuck AWS Support Team has reached out to the internal service team and got a response that the issue was fixed with the EBS volume , and the instance ‘i-0106ab792da490bbb’ now showing in stopped state and Volume state is available.
The issue is fixed
According the support case id which I raised in AWS Support Team the issue was related to operational issue in the Frankfurt
The instance was stuck in stopping state due to the stuck EBS volume. The EBS volume was showing as ‘In Use’ but the instance was showing in stopping state. For EBS volume stuck AWS Support Team has reached out to the internal service team and got a response that the issue was fixed with the EBS volume , and the instance ‘i-0106ab792da490bbb’ now showing in stopped state and Volume state is available.
The issue is fixed
According the support case id which I raised in AWS Support Team the issue was related to operational issue in the Frankfurt
The instance was stuck in stopping state due to the stuck EBS volume. The EBS volume was showing as ‘In Use’ but the instance was showing in stopping state. For EBS volume stuck AWS Support Team has reached out to the internal service team and got a response that the issue was fixed with the EBS volume , and the instance ‘i-0106ab792da490bbb’ now showing in stopped state and Volume state is available.
The issue is fixed
関連するコンテンツ
- 質問済み 6年前
- AWS公式更新しました 10ヶ月前