3回答
- 新しい順
- 投票が多い順
- コメントが多い順
0
There were no status check errors. the gap just before 11 was from when I stopped/started the instance
回答済み 4ヶ月前
0
Firstly I hope helping you. We must to verify if it's a hardware or software or security or network issues ?
回答済み 4ヶ月前
For me it's a windows restrictions maybe firewall or antivirus inside the os. Did you enable the sac in order to troubleshoot your Windows instance via the serial console?
No changes to the windows firewall or antivirus prior to connection loss. The issue that prompted the post happened early in the morning while our team was asleep. The SAC was enabled but was not working when the issue occurred. Once the system is restarted the SAC and system works as expected.
関連するコンテンツ
- 質問済み 6年前
Ok you have a Nitro-based instance . When you tired connecting your EC2 instance Serial Console for Windows. You couldn't maybe because you need To view your account access status to the serial console via (AWS CLI) by typing: aws ec2 get-serial-console-access-status --region you-region If In the output indicates you : { "SerialConsoleAccessEnabled": true } This means that your account is allowed to access to the serial console.
Once the instance comes back up after doing a stop/start I am able to access the serial console for windows without any issues
I had another instance have the same issue tonight. I had read somewhere about trying to add another network interface. I tried that but still was unable to connect to the instance. The serial console did come up but when trying to start a cmd session it timed out. Again there were no failed status checks and the CPU was less than 20% at the time it happened.